Description of problem: Importing the ejb-security-interceptors quickstart into JBDS results in the following jboss-ejb3.xml validation errors. cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. jboss-ejb3.xml /jboss-ejb-security-interceptors/src/main/resources/META-INF line 31 XML Problem Carlo said this is a problem with the jboss-ejb-container-interceptors_1_0.xsd schema. The schema has been uploaded to: http://www.jboss.org/j2ee/schema/jboss-ejb-container-interceptors_1_0.xsd See quickstart Bug 1193543. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is a flaw in the design of container-interceptors. The xml as originally coded at https://github.com/jbossas/jboss-eap/commit/3ad941690b6c7f3c256309ea0edd3eeea68d7af2#diff-15c3e2a4b5220bb357311f6a3c6a6439R23 is wrong. It mixes up interceptors and interceptor-bindings badly. See https://github.com/jbossas/jboss-eap/blob/b7fa0674f42af11e9a3af5b9c04027492166dc49/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/interceptor/inject/ejb-jar.xml#L7 for a pristine spec example. So both xsd and implementation must be redone.
In a backwards-compatible manner of course...
Adding Darran, the quickstart owner, so he is aware of this issue. This will also impact the documentation.
The quickstart issue in the description above is wrong. It should be Bug 1178748.
Created JIRA: https://issues.jboss.org/browse/WFLY-4365