Bug 69040 - Disabling Java gives unhelpful error message for Java adding registration - Could not create Java implementation loader
Summary: Disabling Java gives unhelpful error message for Java adding registration - C...
Status: RESOLVED DUPLICATE of bug 112723
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Error-Messages
  Show dependency treegraph
 
Reported: 2013-09-06 15:12 UTC by Christian Fries
Modified: 2022-05-15 22:39 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Fries 2013-09-06 15:12:29 UTC
Registrating a Java UNO Addin in an LibreOffice for which the JRE is disabled (by
disabling "Use a Java runtime environment" in Perferences->Advanced) will result in the error message

Could not create Java implementation loader

This message is unhelpful.

Fix: Improve the error message to s.th. like
"This add in requires a Java runtime. Please enable the Java runtime in ...."
Comment 1 Christian Fries 2013-09-06 15:13:39 UTC
To reproduce:

- Disable Java runtime in Preferences->Advanced

- Download Obba.zip from http://www.obba.info and install Obba.oxt from "Obba for OpenOffice"
Comment 2 Jean-Baptiste Faure 2013-11-16 14:00:06 UTC
I reproduce the problem with LibreOffice 4.1.4.0.0+ and the master.
This exception is triggered here : http://opengrok.libreoffice.org/s?defs=CannotRegisterImplementationException&project=core

I agree that a more clear error message would be better.

Note: in fact the extension is installed (try a second time to install, you will get a message asking for reinstalling or canceling). 

Best regards. JBF
Comment 3 sdc.blanco 2022-05-15 22:39:05 UTC
Although this might be the first report chronologically, the other report has an analysis about what to do to address the problem.

*** This bug has been marked as a duplicate of bug 112723 ***