I'll have to look closer, it's a ListenerMetaData which is added so perhaps
it is close to a web-fragment part or something and it just happens to be
created with a default constructor and ends up last because its all
defaulted or something...
On Wed, Mar 24, 2010 at 6:17 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
On Wed, Mar 24, 2010 at 12:16 PM, Nicklas Karlsson
> 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.
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597