web.xml only (I mean, if you really wanted to be extreme in the consolidation)<br><br><div class="gmail_quote">On Wed, Nov 25, 2009 at 12:14 PM, Arbi Sookazian <span dir="ltr"><<a href="mailto:asookazian@gmail.com">asookazian@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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?<br>
<br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Nov 25, 2009 at 9:09 AM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">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:<br>
<br>web.xml<br>faces-config.xml<br>persistence.xml<br>
orm.xml<br>beans.xml<br><br>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).<br>
<br>So there are two separate goals here.<br><br>1. Merge vendor extensions into the standard descriptor (Hibernate mappings into orm.xml or persistence.xml, for instance)<br>2. Combine all configurations into a single, consolidated descriptor (web.xml for WAR, ejb-jar.xml for EJB-JAR, and applications.xml for EAR)<br>
<br>-Dan<br clear="all"><font color="#888888"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</font><br></div></div><div class="im">_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br></div></blockquote></div><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>