To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116342
                 Issue #|116342
                 Summary|OXT extension using a signed JAR not working, cryptic 
                        |error message
               Component|udk
                 Version|OOo 3.3 RC8
                Platform|All
                     URL|http://www.christian-fries.de/blog/files/2010-OpenOffi
                        |ceExtension.html
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|kr
             Reported by|cfries





------- Additional comments from [email protected] Fri Jan  7 05:59:04 
+0000 2011 -------
A Java based OpenOffice extension (.oxt) using a signed JAR (inside the .oxt 
bundle) does not register 
in OpenOffice 3.3.0. Instead you see the unhelpful error message:
  ImplementationRegistration::registerimplementation() 
  InvalidRegistryException during registration (prepareRegistry(): source 
registry is empty) 

To reproduce the problem create a .keystore (using keytool) and sign the JAR at 
the -pre-uno-package 
build step: 

<target name="-pre-uno-package"> 
   <signjar jar="${dist.jar}" alias="yourAlias" storepass="yourPassword" /> 
</target>
in your ant build of the .oxt. The resulting .oxt will be dysfunctional.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to