web.xml only (I mean, if you really wanted to be extreme in the
consolidation)
On Wed, Nov 25, 2009 at 12:14 PM, Arbi Sookazian <asookazian(a)gmail.com>wrote:
So referring to point #2 below, what about the case in EJB 3.1 (EE6)
where
you can package JARs in a WAR? Then what? Would we use web.xml only or
web.xml and ejb-jar.xml?
On Wed, Nov 25, 2009 at 9:09 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
> The other use case that was brought up was to merge multiple standard
> descriptors into a consolidated location. So inside of web.xml, we could
> have the configuration for:
>
> web.xml
> faces-config.xml
> persistence.xml
> orm.xml
> beans.xml
>
> The idea is to have one descriptor and support all the different
> configuration schemas that Java EE provides. The result would look something
> like the Seam component descriptor (or Spring's applicationContext.xml).
>
> So there are two separate goals here.
>
> 1. Merge vendor extensions into the standard descriptor (Hibernate
> mappings into orm.xml or persistence.xml, for instance)
> 2. Combine all configurations into a single, consolidated descriptor
> (web.xml for WAR, ejb-jar.xml for EJB-JAR, and applications.xml for EAR)
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
>
http://mojavelinux.com
>
http://mojavelinux.com/seaminaction
>
http://www.google.com/profiles/dan.j.allen
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/weld-dev
>
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen