[
https://issues.jboss.org/browse/WFLY-4365?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on WFLY-4365:
-------------------------------------
This is a flaw in the design of container-interceptors.
The xml as originally coded at
https://github.com/jbossas/jboss-eap/commit/3ad941690b6c7f3c256309ea0edd3...
is wrong.
It mixes up interceptors and interceptor-bindings badly. See
https://github.com/jbossas/jboss-eap/blob/b7fa0674f42af11e9a3af5b9c040274...
for a pristine spec example.
So both xsd and implementation must be redone.
jboss-ejb-container-interceptors_1_0.xsd is invalid
---------------------------------------------------
Key: WFLY-4365
URL:
https://issues.jboss.org/browse/WFLY-4365
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Sande Gilda
Assignee: Weston M. Price
Importing the ejb-security-interceptors [1] quickstart into JBoss Developer Studio
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
jboss-ejb-security-interceptor source is here:
https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel...
The quickstart bug is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1178748
The related bug for the invalid schema for JBoss EAP 6.4 is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1193948
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)