Am Mittwoch, den 24.03.2010, 12:17 -0400 schrieb Dan Allen:
On Wed, Mar 24, 2010 at 12:16 PM, Nicklas Karlsson
<nickarls(a)gmail.com> wrote:
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?"
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.
This would also be a good question on the dev forum. There should be an
internal API where we just add a web-fragment.xml to each deployment.
-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