If you cannot inject into ServletListeners, that's a bug in WAS, as I'm pretty sure with Servlet 3.0 you can.
As for the other stuff, we know there are problems with OWB.
Jason is right. It seems like WAS isn't injecting into servlet listeners. It's actually exactly the same issue Tomcat users are currently running into:
Perhaps it's worth thinking about if it's possible to add some kind off fallback behaviour to that class for situations in which the injection doesn't work correctly. I'm just thinking loud about this because currently Seam Tranaction is completely unusable on Tomcat and WAS.
Could you try to add this to your web.xml:
<context-param> <param-name>org.jboss.seam.transaction.disableListener</param-name> <param-value>true</param-value> </context-param>
That worked! Thanks so much - spent way too much time on that one.
Jason, would you happen to know if there's a way to filter for known issues affecting Seam on OWB? When I encounter these it's sometimes difficult to determine whether they're issues with Seam or issues with OWB.
Being unable to inject into ServletListeners seems like a significant issue if it's indeed part of the spec (I haven't researched this).
That part was in the docs
WRT to the OWB issues, to my knowledge we have had very few people using Seam 3 with OWB, so there probably isn't a label or anything in JIRA to use. This would be a good time to start a label though.
Also, as work on Seam 3 is slowing down, DeltaSpike will be the place to go for truely portable extensions. We have people from Apache, Red Hat, Oracle and others in the community. Anything produced from DeltaSpike will truely be portable.