Hi,
Well, I'm not sure that it should be allowed
I see no major difference between an EAR file including an EJB file +
libraries and an EJB file including an external library file as there is
an extra "packaging" step
And often, when using .jar extension, we expect to find all the classes
at the root.
Also, we can still make an uberjar of all dependencies with tools like
maven when building its EJB.
Regards,
Florent
On 02/09/2012 02:14 AM, Marina Vatkina wrote:
> Experts,
>
> As you know, while it's easy to package a library into a .war file or
> a .ear archive, there is no easy way to do the same for a stand-alone
> EJB module in a portable way. The only current option is to use a
> reference by adding a Class-Path attribute to the Manifest file of the
> EJB .jar file (or another referenced archive) but this is not portable
> as it requires to place referenced library in the specific location of
> the application server file system (in case that .jar file is not used
> from its original location).
>
> Do you thing the EJB spec should allow an EJB .jar file to have a lib/
> directory inside it? If yes, will there be any restrictions that we
> will need to address?
>
> Thank you,
> -marina
>
>
>