<div class="gmail_quote">On Wed, Mar 24, 2010 at 12:16 PM, Nicklas Karlsson <span dir="ltr"><<a href="mailto:nickarls@gmail.com">nickarls@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Yep but this is on implementation level, the JBoss - weld integration sticks the WeldListener in all deployments through meta-data manipulation. Previously it just got the list of listeners and added it to the end of the list (i.e. not with a xml file). I tried putting it first but that didn't help so the question is, "is the ordering done at a later stage?" and "how can we get it first in all cases?" and "can we simulate a web-fragment etc so that the ordering is portable?"</blockquote>
<div><br></div><div>Frankly, I don't understand why JBoss is not using the web-fragment.xml (or emulating it) so that it plays by the Servlet 3.0 rules.</div><div><br></div><div>-Dan</div><div><br></div></div>-- <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>