[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on WFLY-3189: ----------------------------------- With the patch in the above pull request, I've found validation generally works. The following example jboss-ejb3.xml validates with 0 errors: {code} <?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar version="3.1" impl-version="2.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <assembly-descriptor> <s:security> <ejb-name>*</ejb-name> <s:security-domain>testsd</s:security-domain> <s:run-as-principal>SomeUser</s:run-as-principal> <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access> </s:security> </assembly-descriptor> </jboss:ejb-jar> {code} Missing any of the elements inside 'security' shows validation errors, as required elements are missing. I would like to note that the example file used in this JIRA still does *not* validate. I'll re-paste the non-validating example here: {code} <?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar version="3.1" impl-version="2.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> <assembly-descriptor> <s:security> <ejb-name>*</ejb-name> <s:security-domain>testsd</s:security-domain> </s:security> </assembly-descriptor> </jboss:ejb-jar> {code} The reason this does NOT validate is this line here: {code} xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> {code} As far as I can tell, the reason this is failing to validate is because while we have updated the schema in the wildfly and metadata repos, we still have not yet updated the schema at the various web locations, and so specifying the remote addresses is still confusing the catalog. -- This message was sent by Atlassian JIRA (v6.3.1#6329)