Hi;
Sorry but I don't understand the connection of 3rdparty jars licensing and classloading...
If you mean that you should not take an ear file with weblogic.jar and put it on IBM well that's obvious (unless you paid both for their App Server), but you never put the J2EE implementation jar in the ear file because there is no point in that. The J2EE implementation jar is allways in the system classpath other wise the App Server would not run.

-----Original Message-----
From: Tim Wood [mailto:timwood0@PACBELL.NET]
Sent: Monday, July 28, 2003 8:14 PM
To: J2EE-INTEREST@JAVA.SUN.COM
Subject: Re: Class Loading in Web Tier

At 01:44 AM 07/28/03, you wrote:
>hi;
>I don't know much about jboss, but in web sphere you can choose the class loading scheme to load from the war first.
>try to put all your 3rd party jars in the web-inf/lib so your war is portable and self contained. in this case, the only time you will go to the system classpath is for loading the App Server runtime classes (there probably is a websphere.jar some where which is the J2EE implementation of IBM).

(Newbie comment here, please correct if wrong...)
As an application provider, you may not have the right to copy 3rd-party jars into the .war/.ear you distribute.  The best balance of portability and observance of license rights would seem to be to devise a robust means of finding required 3rd-party libs from standard installation locations.  Or specifying the locations might be a manual step to deploying the distributed application, i.e., a "deployment classpath".

Thanks,
TW

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff J2EE-INTEREST".  For general help, send email to
listserv@java.sun.com and include in the body of the message "help".