Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
On 07/26/10 15:20, TJ Frazier wrote: On the page http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format I added a little description, for a better overview of .oxt files. However, rony's problem relates to deploying old extensions, which might need another sentence in the Note in the lead section. Something like, "For an extension previously deployed as a jar," [if that's a proper description] "the entire jar should be exported as above." [if that's the proper solution]. Not sure it is worth to discuss that in the Dev Guide at all. (And "the entire jar should be exported as above" would IMO not help to avoid the trap that caught Rony, either.) -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
Hi, Oliver, Stephan, On 7/26/2010 06:53, rony wrote: Hi Stephan, On 26.07.2010 09:20, Stephan Bergmann wrote: To avoid a misunderstanding: :) There was no misunderstanding at all on my side, but plain ignorance and missing experience/knowledge on my side, never having created an oxt-extension! (To my defense, I tried to research the developer guide and various search engines, but have not found the clues that would have helped me master this particular challenge.) You cannot rename ScriptProviderForooRex.jar to ScriptProviderForooRex.oxt and include a description.xml and META-INF/manifest.xml in that zip. Instead, you need to create a new zip ScriptProviderForooRex.oxt that includes ScriptProviderForooRex.jar, description.xml, and META-INF/manifest.xml. Then, a manifest:full-path="ScriptProviderForooRex.jar" should work. Thank you *very* much for this vital information, which may have been so obvious for you and everyone else who has created Java based extensions, but was new for me! Just applied it and it now works like a charm! Again, kudos to you and Oliver! ---rony P.S.: Now, in hindsight (after your explanations) this makes perfect sense! On the page http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format I added a little description, for a better overview of .oxt files. However, rony's problem relates to deploying old extensions, which might need another sentence in the Note in the lead section. Something like, "For an extension previously deployed as a jar," [if that's a proper description] "the entire jar should be exported as above." [if that's the proper solution]. (I'm out of my depth here: AFAIK, jars contain peanut butter. Knowledgeable help would be appreciated.) -- /tj/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
Hi Stephan, On 26.07.2010 09:20, Stephan Bergmann wrote: > To avoid a misunderstanding: :) There was no misunderstanding at all on my side, but plain ignorance and missing experience/knowledge on my side, never having created an oxt-extension! (To my defense, I tried to research the developer guide and various search engines, but have not found the clues that would have helped me master this particular challenge.) > You cannot rename ScriptProviderForooRex.jar to > ScriptProviderForooRex.oxt and include a description.xml and > META-INF/manifest.xml in that zip. Instead, you need to create a new > zip ScriptProviderForooRex.oxt that includes > ScriptProviderForooRex.jar, description.xml, and > META-INF/manifest.xml. Then, a > manifest:full-path="ScriptProviderForooRex.jar" should work. Thank you *very* much for this vital information, which may have been so obvious for you and everyone else who has created Java based extensions, but was new for me! Just applied it and it now works like a charm! Again, kudos to you and Oliver! ---rony P.S.: Now, in hindsight (after your explanations) this makes perfect sense! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
On 07/25/10 23:24, rony wrote: Is there something I must also denote in the "description.xml" file to you need a "META-INF\manifest.xml" where you list all your files, for example: .. cut (thank you very much for that very helpful snippet!) ... http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format Thank you very much for this link as well! Here is my current, timid "manifest.xml", which does not cause the "RegistrationClassName" to be followed: http://openoffice.org/2001/manifest";> To avoid a misunderstanding: You cannot rename ScriptProviderForooRex.jar to ScriptProviderForooRex.oxt and include a description.xml and META-INF/manifest.xml in that zip. Instead, you need to create a new zip ScriptProviderForooRex.oxt that includes ScriptProviderForooRex.jar, description.xml, and META-INF/manifest.xml. Then, a manifest:full-path="ScriptProviderForooRex.jar" should work. -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
Hi Oliver,
thank you *very* much for your hint and pointer!
Unfortunately, I have not found a means to get the class registered. Do
I have to explicitly name that class to register in the
"META_INF/manifest.xml" (and if so, how would that be done)? Currently
the "META-INF/MANIFEST.MF" contains the appropriate entry
("RegistrationClassName:
com.sun.star.script.framework.provider.oorexx.ScriptProviderForooRexx").
On 25.07.2010 19:19, Oliver Brinzing wrote:
>> Is there something I must also denote in the "description.xml" file to
>>
> you need a "META-INF\manifest.xml" where you list all your files, for example:
>
... cut (thank you very much for that very helpful snippet!) ...
> http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format
>
Thank you very much for this link as well!
Here is my current, timid "manifest.xml", which does not cause the
"RegistrationClassName" to be followed:
http://openoffice.org/2001/manifest";>
Did leave out the "manifest:full-path" attribute to no avail, using "."
instead of "%origin%" or using "ScriptProviderForooRexx.oxt" would not
make a change. Supplying the name of the jar-file itself did not help
either.
Running "unopkg list --shared" copyin and pasting the information about
that oxt gives:
Identifier: org.oorexx.uno-via-BSF4ooRexx
Version: 4.04
URL:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/F.tmp_/ScriptProviderForooRexx.oxt
is registered: n/a
Media-Type: application/vnd.sun.star.package-bundle
Description: This extension to OpenOffice.org (OOo) adds the easy to
learn,
yet powerful scripting language "Open Object Rexx (ooRexx)".
As a result it becomes possible to add and deploy macros programmed
in ooRexx from within OOo.
ooRexx:http://www.ooRexx.org
BSF4ooRexx: http://wi.wu.ac.at/rgf/rexx/bsf4oorexx/current/
bundled Packages: {
}
Greatful for any further hints/suggestions!
---rony
Re: [dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
Hi, > Is there something I must also denote in the "description.xml" file to you need a "META-INF\manifest.xml" where you list all your files, for example: http://openoffice.org/2001/manifest";> http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format Regards Oliver -- GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45 signature.asc Description: OpenPGP digital signature
[dev] Changed an extension from ".jar" to ".oxt", now extension gets installed but cannot be used ?
Hi there,
currently (for many years) I have been deploying a scripting extension
using a ".jar" file, named "ScriptProviderForooRexx.jar" (adding the
ooRexx language to OOo, such that ooRexx scripts can be dispatched via
OOo as well).
Now, this weekend I wanted to change the filetype to ".oxt"
("ScriptProviderForooRexx.oxt") and adding a "description.xml" file with
a few bells and whistles (icon, description, version number). At first
everything seemed to be working o.k., the extension manager was able to
install and remove the extension, displaying all what "description.xml"
contained.
However, the scripting engine does not get registered, it seems,
although nothing else got changed (just added "description.xml" and two
aubdirectories, "images" and "information", to contain files that are
referred to by "description.xml"). With other words, there is still a
"META-INF/MANIFEST.MF" (unedited as of yet), containing a
"RegistrationClassName":
Manifest-Version: 1.0
RegistrationClassName: com.sun.star.script.framework.provider.oorexx.S
criptProviderForooRexx
It seems that the extension manager is either not handling this (or not
expecting an extension to the OOo scripting framework), at least not in
the way I had expected it to.
The "description.xml" file contains the following elements:
description (root element)
version
identifier
dependencies
publisher
release-notes
display-name
icon
extension-description
Is there something I must also denote in the "description.xml" file to
cause the extension to be identified and registered as an extension to
the OOo scripting framerwork, or am I missing something obvious ?
[P.S.: Just renaming the extension back to '.jar' makes everything work
again, but I loose the "description.xml" stuff, which is a little bit
unfortunate.]
TIA,
---rony
