[weld-dev] Ordering of servlet listeners

[Nicklas Karlsson]

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 at gmail.com> wrote:

> On Wed, Mar 24, 2010 at 12:16 PM, Nicklas Karlsson <nickarls at 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.
>
> -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
>



-- 
---
Nik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20100324/2b50a7b9/attachment-0001.html