I beleive that orion.jar has a classpath set in the manifest file. Take a
look at "manifest.mf" in the orion jar.
Mike
- Original Message -
From: "Kemp Randy-W18971" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Monday,
The orion jar is using the jar extension mechanism. If you look at
orion.jar's manifest, you'll see what jars are being added to the classpath
automatically. You can read more about the jar extension mechanism on Sun's
site.
Andre
-Original Message-
From: Geoffrey Marshall [mailto:[EMA
Hello Geoffrey,
from the orion.jar manifest, the classpath is:
xerces.jar ejb.jar
jndi.jar jdbc.jar jta.jar parser.jar jaxp.jar xalan.jar
tools.jar jsse.jar jnet.jar jcert.jar activation.jar mail.jar
saxon.jar
After that comes (globally)
$(ORIONHOME)/lib
and inside each
At 09:29 23.04.2001 , you wrote:
>Hello all!
>
>Can anyone tell me what Orion is doing with the CLASSPATH. I suspect it
>is building
>its own or adding to mine simply because it knows how to find certain jars
>that I have not specified anywhere.
>
>Any info appreciated...
do yourself a favour
Have a look at META-INF/MANIFEST.MF inside orion.jar, and you'll see
Orion's classpath. Orion uses its own set of classloaders, which have nice
features like automatically picking up any jar/zips from orion/lib, so you
just drop things in there and they work.
On Mon, 23 Apr 2001, Kemp Randy-W1897
I believe it is internally setting it. When I transported the Orion and
Orion Primer examples (www.jollem.com) to Jboss (www.jboss.org) as a
learning exercise, I had to define the package settings externally in my
classpath for jboss. For Orion, I didn't have to do this, but I don't know
what's
