you can manipulate orions "manifest.jar". The classpath is specified in
there
----- Original Message -----
From: "Matt Krevs" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Cc: "Steve Brown" <[EMAIL PROTECTED]>
Sent: Wednesday, December 13, 2000 3:57 AM
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?
>
>
