It's currently solved in weld-int by adding the WeldListener first in the
list of the applications listeners.
On Thu, Apr 8, 2010 at 1:45 PM, Pete Muir <pmuir(a)redhat.com> wrote:
On 24 Mar 2010, at 16:17, Dan Allen wrote:
> On Wed, Mar 24, 2010 at 12:16 PM, Nicklas Karlsson <nickarls(a)gmail.com>
> 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
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.
You mean to add the WeldListener? Because the Weld support in JBoss AS
predates Servlet 3.0 support ....
It should be trivial to switch to using a web.xml fragment, using the same
system we have to insert faces-config.xml into the deployment, if this will
actually help with Nik's problem?