Laird, the idea is not to kick out ear. The examples that you give are
complettelly valuable : ear should be used when there are connectors and/or
several wars (or skinny wars as you say). But war should really become the
default packaging for common web applications.
On Fri, Aug 31, 2012 at 7:50 AM, Laird Nelson <ljnelson_at_gmail.com> wrote:
> On Thu, Aug 30, 2012 at 10:42 PM, Markus Eisele <myfear_at_web.de> wrote:
>
>> So, as long as we keep the additional packaging options for e.g. RARs
>> with EAR format only.
>>
>
> Yes, please; please don't let .ear files languish—if you have an
> application-specific connector, which is not rare, they are the only way to
> do things by the book.
>
> Another use case: bundling different JAX-RS-compliant applications (skinny
> wars) that have their JAX-RS resources actually stored and auto-discovered
> in the ear file's lib directory; makes end user customization/packaging a
> lot easier.
>
> Please don't kick the .ear file to the curb! :-)
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>
>
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org> |
Twitter<http://twitter.com/agoncal>|
LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org> |
Devoxx France <http://www.devoxx.fr>