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-W18971 wrote:
> 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 really going on under the hood.
>
> -----Original Message-----
> From: Geoffrey Marshall [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 23, 2001 11:30 AM
> To: Orion-Interest
> Subject: Orion CLASSPATH
>
>
> 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...
>
> --
>
> Geoffrey W. Marshall Director of Development
> -------------------------------------------------------
> t e r r a s c o p e phone (415) 951-4944
> 54 Mint St #110 direct (415) 625-0349
> San Francisco, CA 94103 fax (415) 625-0306
> -------------------------------------------------------
>
>
