Issue 75316 - CWS sb69 Followup: Handle Exception when installing extension with insufficient Java version
Summary: CWS sb69 Followup: Handle Exception when installing extension with insufficie...
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-12 14:46 UTC by joerg.skottke
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
First step for a fix (10.71 KB, patch)
2007-04-02 10:43 UTC, Stephan Bergmann 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2007-03-12 14:46:37 UTC 
This is a follow up to issue #73665: When installing the extension (attachment
from #73665) we get quite an ugly exception. Please handle it gracefully.
Comment 1 joerg.skottke 2007-03-12 14:49:33 UTC 
Please use something like Sun JRE 1.4.2 as the default java in the office
application to install this extension.
Comment 2 joachim.lingner 2007-03-23 14:28:16 UTC 
I would regard this as nice to have.  We also do not check if a c++ component
requires a C runtime which is currently not available in OOo.

Even if we provided a dependency in the description.xml of the extension, that
determines the version, it is not sure that later the same java is used in OOo
as at the time of deployment. 

Our class loader could perhaps check the required java version and  complain.
Comment 3 Stephan Bergmann 2007-04-02 10:43:45 UTC 
Created attachment 44158 [details]
First step for a fix
Comment 4 Stephan Bergmann 2007-04-02 10:52:18 UTC 
The attached jurt.patch (a cleanup of com.sun.star.comp.loader.JavaLoader
activate and writeRegistryInfo methods, to properly handle
java.lang.LinkageError) solves the issue partly:  Now, a UNO
com.sun.star.loader.CannotRegisterImplementationException instead of a Java
Error translated into a com.sun.star.uno.RuntimeException is thrown, but unopkg
only displays

  ERROR: An error occurred while enabling: JavaComponent.uno.jar

This can probably be improved (e.g., by displaying exception type/message as
further details) in the extension manager.
Comment 5 joerg.skottke 2007-11-28 12:04:50 UTC 
What is the status of this task?
I set the preliminary target to 2.4 (was 2.x which is about to become obsolete)
Comment 6 joachim.lingner 2007-12-07 15:39:26 UTC 
Retargeting to 3.0
Comment 7 joachim.lingner 2008-05-30 15:27:42 UTC 
Retargeted.