Stephen Coy <[EMAIL PROTECTED]> wrote on 13/07/2008 21:07:57: > In JEE5, jars in an EAR's "lib" directory do not need to be in the EJB > jar's manifest classpath.
Ah. Thanks makes it a lot clearer! Thanks for clearing that up for me. > In J2EE 1.3/1.4 these jars normally need to be in the EJB jar's > manifest classpath, whether or not they are in a "lib" directory. If > they are in a "lib" directory, then the manifest classpath entries > must include "lib/" for each jar. > > Now it's possible that WAS 5.1 had a non-portable extension that had > the JEE5 behavior - I know that WebLogic certainly had a similar > feature. But this behavior was not added to the standard until JEE5. > > In any event, Glen does not mention EAR files at all, so I was just > trying to establish what he was trying to do. ********************************************************************** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. **********************************************************************
