project_key: JBPAPP6 AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation is found in the class. [The specification|http://docs.oracle.com/javaee/6/api/javax/interceptor/AroundInvoke.html] says: {panel} A class must not declare more than one AroundInvoke method. {panel} The JBoss AS allows more such methods and then it chooses one of them which is used as the interceptor. It becomes even more important to check the interceptor validity now with the new feature introduced by AS7-5897 (server side non-EE interceptors for EE invocations).
Link: Added: This issue is related to AS7-5897
Test (ignored for now) added in https://github.com/jbossas/jboss-as/pull/3892 {{org.jboss.as.test.integration.ejb.container.interceptor.ContainerInterceptorsTestCase}} {code} @Deployment(name = "incorrect-deployment") @ShouldThrowException(Exception.class) public static JavaArchive createIncorrectDeployment() { {code}
Upstream PR : https://github.com/wildfly/wildfly/pull/6104 PR : https://github.com/jbossas/jboss-eap/pull/1164
Verified in 630ER2. The regression test passes. (e.g. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-6x-as-testsuite-RHEL-matrix-openJDK6/116/jdk=openjdk-1.6.0-local,label_exp=RHEL5%26%26x86_64/testReport/org.jboss.as.test.integration.ejb.container.interceptor/ContainerInterceptorsTestCase/testMultipleAnnotatedInovkeAroundClass/)