[ https://issues.jboss.org/browse/WFLY-2611?page=com.atlassian.jira.plugin.... ] Tomas Remes updated WFLY-2611: ------------------------------ Description: There are three ways, how can user specify custom JSF action listener: 1. Method binding - with actionListener param. This case is ok, meaning CDI injection and interceptor works for given method/bean. 2. Providing custom implementation - <f:actionListener type="org.jboss.jsf.listeners.MyActionListener"/>. In this case CDI doesn't work at all for processAction method of given class. 3. Defining in faces-config - in this case CDI injection works, but interceptor is not executed. Reproducer available at https://github.com/tremes/javaee7-samples/tree/cdi-testing/jsf/jsf-listen.... Test can be executed with "mvn clean test -Pwildfly-managed-arquillian" or "mvn clean test -Pwildfly-remote-arquillian" and IMHO all should pass. was: There are three ways, how can user specify custom JSF action listener: 1. Method binding - with actionListener param. This case is ok, meaning CDI injection and interceptor works for given method/bean. 2. Providing custom implementation - <f:actionListener type="org.jboss.jsf.listeners.MyActionListener"/>. In this case CDI doesn't work at all for processAction method of given class. 3. Defining in faces-config - in this case CDI injection works, but interceptor is not executed. Producer available at https://github.com/tremes/javaee7-samples/tree/cdi-testing/jsf/jsf-listen.... Test can be executed with "mvn clean test -Pwildfly-managed-arquillian" or "mvn clean test -Pwildfly-remote-arquillian" and IMHO all should pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira