[seam-issues] [JBoss JIRA] (SEAMTRANSACTION-15) Seam Transaction is no longer working with servlet containers like Tomcat that don't support CDI injection in listeners

Miguel Z created SEAMTRANSACTION-15: --------------------------------------- Summary: Seam Transaction is no longer working with servlet containers like Tomcat that don't support CDI injection in listeners Key: SEAMTRANSACTION-15 URL: https://issues.jboss.org/browse/SEAMTRANSACTION-15 Project: Seam Transaction Issue Type: Quality Risk Affects Versions: 3.1.0.Final Environment: Apache Tomcat 7.0.25 Reporter: Miguel Z Assignee: Stuart Douglas Lack of transaction injection causes: java.lang.NullPointerException org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:106) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987) org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:307) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) java.lang.Thread.run(Thread.java:662) The implementation has changed after SEAM Transaction 3.1.0.Beta5: https://github.com/seam/transaction/commit/64ef15aee882d8809a42749fc2283a... Instead of a filter there is now a listener doing the job. This "better" implementation excludes all users that use non-EE-containers like Tomcat that don't support @Inject in listeners: e.g. Tomcat 7.0.25 startup: ... INFO: Tomcat 7 detected, CDI injection will be available in Servlets and Filters . Injection into Listeners is not supported ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira