Emmanuel Bégué wrote:
Hello Bernd (with a d, sorry about that in my last message!),
Thank you very much, I tested it and it worked
(in OOO300m9, build 9358).
What I don't understand though is that I had to
declare Saxon9 in the classpath setting (as you
said): but I thought OOO3 shipped with Saxon9?
Well internal ClassLoader Mechanisms changed since OpenOffice.org 2.3
and are well a little bit complicated now. The jars shipped with OOo are
no longer on the global classloader which uses the classpath but there
are other classloaders loading those classes in effect.
What should be enough tough is to reference a relative path to
saxon9.jar in the MANIFEST of the library providing the saxon extension.
Just didn´t bother to do so because for now this was just some kind of
quick and experimental demonstration on what can be done. Also you
probably would like to change that saxon extension in a way so that the
java window is only created on the first xsl:message and not just always
when the XSL-transformation starts even if no xsl:message is ever executed.
(saxon9.jar is indeed found in
OpenOffice.org 3\Basis\program\classes)
From here I have new questions:
- what XSLT processor is used when the classpath
for Saxon9 is not declared / what is the "out of
the box" XSLT processor?
It is saxon9 but OOo loads it from a ClassLoader that is not the global
Application wide ClassLoader.
See this blog entry from Stephan Bergman for some background information:
http://blogs.sun.com/GullFOSS/entry/is_your_java_extension_ready
- is there a way to "automate" / simplify those classpath
settings on a given OOO installation? (from a batch
file for example, which would write directly to a
config file?) -- because it is doubtfull the users of
this filter will be willing to do it themselves...
What you really would want to do is to create an OpenOffice.org
extension that your users can just install/deinstall via
OpenOffice.org´s extension mechanism this would install your XML Filter
plus the jar with the saxon extension and than in the saxon extension
you would have that MANIFEST entry with the relative path to the
saxon9.jar. Providing your filter as an OOo extension is the most
simplification/automation you can get for your users.
Probably you also want to publish that extension later on
http://extensions.services.openoffice.org if it is something for general
use.
All kinds of information regarding OOo Extensions including how to
create them can be found in the OOo Wiki at
http://wiki.services.openoffice.org/wiki/Extensions
Information on how to provide an XML Filter as an Extension can be found
at http://wiki.services.openoffice.org/wiki/Filter_extensions
Many thanks again for all your help!
Regards,
EB
Regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
