So I take it you&#39;re specifically referring to components.xml and pages.xml (and not faces-config.xml)?  If you could fine, but then what happens if the dev wants to port to another integration fwk and eliminate Seam3 (not that anybody would really do that!)  Instead of deleting Seam-specific xml files, you must edit EE-specific xml files.  But I guess that may not be a big deal.<br>
<br>It seems cleaner to me and easier to read/understand the configs if you have separate Seam-specific xml files for it...  Of course, it may be easier for users b/c it&#39;s less files to worry about...<br><br>I would consider Seam to be an extension of JEE, so if you &quot;collapse&quot; data in EE-specific xml files, then that may be considered an intrusion of sorts...<br>
<br><div class="gmail_quote">On Wed, Nov 25, 2009 at 6:02 AM, Pete Muir <span dir="ltr">&lt;<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>&gt;</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;">
Hi Jason,<br>
<br>
Something that came up during our Seam team meeting was the issue of config files again. We wanted to investigate again why we can&#39;t put namespaced elements into existing java ee config files such as application.xml, ejb-jar.xml, web.xml, but instead have to provide our own... Of course, this is non portable, but it would make life easier for users in our opinion.<br>

<br>
Previously we have heard that this would cause us to fail the TCK, but given that this code would never run in the EE TCK, I can&#39;t see how.<br>
<br>
Any ideas?<br>
<br>
Pete<br>
_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">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>
</blockquote></div><br>