I thought they were fired in the order listed in web.xml.
On 24/03/10 17:20, Nicklas Karlsson wrote:
I'm tinkering with the servlet listener -> CDI event bridge
in the seam-servlet module and noticed that currently the WeldListener
is placed last in the PostWebMetadataDeployer in weld-int.
I changed this (and verified it with the debugger) but still my
own servlet listener fires first (expecting the contexts to be up),
causing problems. Any theories as to why this is? How could we
the WeldListener is the first one to fire?
weld-dev mailing list