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
