[jboss-jira] [JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

[Michael Hauke (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003095#comment-13003095 ] 

Michael Hauke commented on WFLY-3189:
-------------------------------------

Hi Rob,

as far as I see all the failed tests are in "testsuite/integration/smoke" and relate to "jboss-ejb-clustering_1_0.xsd" (added by the pull the request).

"testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/StandardConfigsXMLValidationUnitTestCase.java" has a static initializer, which adds some XSD to a set called "EXLUDED_SCHEMA_FILES", starting here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/subsystem/xml/AbstractValidationUnitTest.java#L71, with a reference to a Bug in Xercesj, including "jboss-ejb3-2_0.xsd", "jboss-ejb3-spec-2_0.xsd", "jboss-ejb-security_*.xsd" and so on, i.e. probably all the schemata redefining the "javaee" name space.

I added "jboss-ejb-clustering_1_0.xsd" to this set and ran the tests in "testsuite/integration/smoke" and got no failures, Maven says: "Tests run: 109, Failures: 0, Errors: 0, Skipped: 2", I don't know what's about the skipped tests.

I'd propose to add "jboss-ejb-clustering_1_0.xsd" to the excluded XSD. I don't know how to amend your pull request to include that. Maybe you could do that?

> Error validating jboss-ejb3.xml.
> --------------------------------
>
>                 Key: WFLY-3189
>                 URL: https://issues.jboss.org/browse/WFLY-3189
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 8.0.0.Final
>         Environment: WildFly 8.0.0.Final
>            Reporter: shinzey shinzey
>            Assignee: David Lloyd
>         Attachments: p.patch
>
>
> I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error:
> {noformat}
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33]
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37]
> src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39]
> {noformat}
> The jboss-ejb3.xml is quite simple:
> {code:xml}
> <?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}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)