Re: jre/lib/ext jars not loaded
peter-4lf8KW9E9MLMqX/[email protected] Wed, 18 Feb 2004 12:22:46 +1100
| Newsgroups | gmane.comp.java.jcontainer.interest |
|---|---|
| Message-ID | <002401c3f5bd$b6f32d00$21e7809d@fisg2> |
Hi, Sorry not to get back to you - rl is crazy atm. You are almost correct. By default the "ext" (aswell as the "endorsed") jars are available for all the .sar applications. However the location that the JVM looks for the "ext" (and "endorsed") jars in is defined by a system property (java.ext.dirs and java.endorsed.dirs" IIRC). From memory Loom overides these properties to something like $LOOM_HOME\lib\ext, $LOOM_HOME\lib\endorsed or something similar. This was because we were having conflicts between different XML parsers and what not at one stage. I would look at the loom.sh/run.bat scripts to verify this. Hope this helps! ----- Original Message ----- From: "Joerg Buchberger" <[email protected]> To: <jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org> Sent: Wednesday, February 11, 2004 9:15 PM Subject: jre/lib/ext jars not loaded > Hi there. > > Are jars located in jre-home/lib/ext automatically loaded (accessible) > for SARs running in Loom? > Do Loom and Phoenix have the same behaviour in this respect? > > Cheers, > Joerg > > > _______________________________________________ > jcontainer-interest mailing list > jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org > http://lists.codehaus.org/mailman/listinfo/jcontainer-interest > >