Marina Vatkina wrote:
> I don't think we explode jars in the lib directory (either in an ear
> or a war).
>
You think correctly.... and it makes sense, since there wasn't anything
special about jars in those locations... they were pojas (plain old java
archives), suitable for adding to a class path and not much else.
In Java EE 6, it looks like there is the notion that some of the content
of WEB-INF/lib will not be pojas... The possible effects of that change
on file layout and build processing for directory deployment is pretty
important to me.
Thanks,
vbk
> -marina
>
> Vince Kraemer wrote:
>> It looks like Java EE 6 will allow web apps to contain EJB
>> implementations. When the EJBs are in the classes directory, it is
>> pretty obvious how this will affect directory deployment and how an
>> IDE might leverage that capability of v3.
>>
>> In the situation where the web app's lib directory contains a jar
>> that has EJBs in it (which makes the web app kind of earrish, to my
>> way of thinking)... will there be a way to eliminate the jar creation
>> step of the build?
>>
>> For example, in the v2/ear case, a developer can eliminate the jar
>> packaging step when they build an ear that contains a web app and an
>> ejb-jar... by carefully setting the destdir attribute of their javac
>> task... http://ant.apache.org/manual/CoreTasks/javac.html
>>
>> It would be nice to be able to do something like this for earrish web
>> apps in v3...
>>
>> What is the current thinking in this area?
>>
>> vbk
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>