Yes, you can modifie the classpath with the jar-file.
Have a look at the "meta-inf/manifest.mf" file in the orion.jar, there you
can edit the classpath which you need.
For using Cocoon, I had to insert the cocoon-jars at the front of the list.
May be it's the same solution at your problem. Try to add your xalan-jars
also at the front of the list.
Best regards,
Tom
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Matt Krevs
Sent: Wednesday, December 13, 2000 3:58 AM
To: Orion-Interest
Cc: Steve Brown
Subject: Classloader issues using Xalan with Orion
My web app works fine except for some Xalan transform issues (involving
extension fuctions). These dont work because in a typical deployment the
classes cant be found even though the jars live in the orion/lib or
myapplication/WEB-INF/lib directory.
I guess the extension functions of Xalan have their own class loaders which
seem to ignore the classloader(s) used by orion.
A solution was posted a while ago saying to put all the extension
classes/jars in the jre/lib/ext directory which does fix the problem.
However this isnt all that nice a solution for deployment. Id rather leave
the classes where they are and configure Orion accordingly.
Is there any way to start orion using the -jar orion.jar commandline but to
also maintain a classpath in the VM?
Has anyone else had this particular problem or a similar problem with other
3rd party software?
Any ideas?
