Hi,
How are things going.
I finally managed to get onto a project that is working on reasonable
technology.
Rosco still working with you?
Ciao
Frank
On 13/07/2008, at 9:07 PM, Stephen Coy wrote:
In JEE5, jars in an EAR's "lib" directory do not need to be in the
EJB jar's manifest classpath.
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.
Thanks,
Steve C
On 13/07/2008, at 4:47 PM, ChrisGWarp wrote:
Stephen Coy-3 wrote:
The usual way of doing this is to package the EJB jar together with
its dependencies in an EAR file. In a JEE5 environment the deps can
either go in a "lib" directory in the EAR or (and for J2EE 1.3/4) be
at the root of the EAR and a manifest classpath entry added to the
EJB
jar.
There is no special restriction or requirement for where the
additional jars
can go.
We were using a lib directory in the root of the ear quite happily
with
WebSphere 5.1 (J2EE 1.3).
The above post implies (the way that I read it) that J2EE 1.3/4
must go into
the root of the ear, which is not the case.
-Chris
--
View this message in context:
http://www.nabble.com/EJB-Jar-packaging-tp18402174p18426698.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
