Hi Stephan,
reading
http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=19584
I wonder how filter/source/xsltfilter/XSLTransformer.java gets it right.
The intention was to switch to saxon9 for XML Transformations for OOo
3.2 as far as I know.
I see a call to
setContextClassLoader(this.getClass().getClassLoader()) in
XSLTransformer.java
And I see a ClassPath Entry for saxon9.jar in the MANIFEST.MF of
XMLFilter.jar.
is having those two things already enough?
Your blog
http://blogs.sun.com/GullFOSS/entry/is_your_java_extension_ready
also mentions a UNO-Type-Path entry for the Manifest that must be set if
UNO Types are used which is the case for XMLTransformer. There is a
UNO-Type-Path in XMLFilter.jar´s MANIFEST.MF but it is empty. Is this an
error?
Where can I find more information on what value should be put into the
UNO-Type-Path?
I have tried some experimental Saxon extensions and got some
problems/questions:
saxon9.jar loaded from XMLFilter.jar would create Objects using
class.forName() from the jar with the extensions. This jar I currently
put on the OOo classpath. I assume that if I would install this as a OOo
extension I do no longer need to put it onto the global OOo classpath,
is this correct? Do i need to set a contextClassLoader in the extension
or is it already enough that XMLTransformer.java did this and my
extension would inherit the context-classloader set by XMLTransformer.
Also I currently seem to get into trouble when trying to use UNO
interfaces from within those extensions, could this be caused by a
missing UNO-Type-Path entry? If yes how must this look like?
Kind regards,
Bernd Eilers
Stephan Bergmann wrote:
On 01/29/09 06:51, Emmanuel � wrote:
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?
Didn't read through this thread too closely, but I assume you are having
trouble with Java's context class loader. See
<http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=20702> for
pointers.
-Stephan
---------------------------------------------------------------------
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]
