I would not consider this a blocking bug. I documented it as a known issue here: https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md#use-red-hat-jboss-developer-studio-or-eclipse-to-run-the-quickstarts

Strange, currently I'm not seeing any validation errors against the sample xml with the IIOP descriptor using JAXP and straight Java code. However, I am seeing validation errors with xmllint and other utilities. Carlo, could you specify how you produced this error> I am attaching my files as well so someone can verify that validation works fine and I didn't miss anything.

Weston, this all started with this bug: 
    https://bugzilla.redhat.com/show_bug.cgi?id=1184236

Errors occurred importing the jts [1] quickstart into JBDS, 

We added a warning to the JBDS known issues [2].


[1] https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.0.x-develop/jts

[2] https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts

*** Bug 1193543 has been marked as a duplicate of this bug. ***

Thanks. Ill have a closer look.

Thanks. Ill have a closer look.

Hi Weston,

Follow the steps below to reproduce the issue.

1. Configure your Maven settings to use the following repositories (see attached example):
        http://maven.repository.redhat.com/techpreview/all
        http://maven.repository.redhat.com/earlyaccess/all/
        http://jboss-developer.github.io/temp-maven-repo/
        http://repository.jboss.org/nexus/content/groups/public/
2. Checkout the quickstarts from the default 7.0.x-develop branch: 
        https://github.com/jboss-developer/jboss-eap-quickstarts
3. Start JBoss Developer Studio 8
4. Import the 'jts' quickstart into JBoss Developer Studio.
5. Note the Problems window displays 2 errors and 10 warnings. Screen shot is attached. This is the error that the bug refers to:

    cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.    jboss-ejb3.xml    /jboss-jts-application-component-2/src/main/resources/META-INF    line 30    XML Problem

Please let me know if you have any other questions.

Thanks,
Sande

Created attachment 1026665 [details]
Screen shot of the error

This is a screen shot of the the error that displays when you import the `jts` quickstart.

Created attachment 1026670 [details]
Maven settings.xml file

Thanks Sande, especially the settings file.

I have a workaround for this, but it's a solution that neither Carlo or myself care for. It appears there are duplicated elements across namespaces/schema that need some explanation. As Stuart Douglas 'maintains' the IIOP schema, or was at least the last one to work with it, I'm going to speak with him about why this was needed. Stuart was on PTO last week but has returned. I will talk with him this morning.

Sorry, forgot to include the workaround. In order to get past the current issue, your XML file should read: 

<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
               xmlns="http://java.sun.com/xml/ns/javaee"
               xmlns:iiop="urn:iiop"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
                  http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
                  urn:iiop http://www.jboss.org/j2ee/schema/jboss-ejb-iiop_1_0.xsd"
               version="3.1"
               impl-version="2.0">
    <assembly-descriptor>
		<iiop:iiop>
			<ejb-name>ejbName</ejb-name>
			<iiop:ejb-name>ejbName</iiop:ejb-name>
			<iiop:binding-name>bindingName</iiop:binding-name>
			<iiop:ior-security-config></iiop:ior-security-config>
		</iiop:iiop>		
    </assembly-descriptor>
</jboss:ejb-jar>

The duplication comes obviously in the ejbName portion. Ideally, the ejbName element should be taken from the javaee:jboss-assembly-descriptor-bean-entryType complex which the iiopConfigType extends using an extension base. This is not happening and as a result, the ejbName needs to be duplicated. I can't see why we would need this. 

Again, I will speak with Stuart to verify. If we can remove it, the ejbName will be taken from the IIOP config and the schema should validate with no issues. 

Note, there are a few other bugs around this issue, some are duplicates. I am trying to track the rest down. I marked one as duplicate recently and I think I can track back from there.

Note that using the work-around mentioned in the description gives an error in the parser:
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[34,51]
Message: found: CHARACTERS, expected START_ELEMENT or END_ELEMENT
	at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1250)
	at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:64)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.AbstractEJBBoundMetaDataParser.processElements(AbstractEJBBoundMetaDataParser.java:66)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.IIOPMetaDataParser.parse(IIOPMetaDataParser.java:50)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.IIOPMetaDataParser.parse(IIOPMetaDataParser.java:45)
	at org.jboss.metadata.ejb.parser.spec.ExtendingMetaDataParser.processElement(ExtendingMetaDataParser.java:83)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossAssemblyDescriptorMetaDataParser.processElement(JBossAssemblyDescriptorMetaDataParser.java:59)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossAssemblyDescriptorMetaDataParser.processElement(JBossAssemblyDescriptorMetaDataParser.java:42)
	at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65)
	at org.jboss.metadata.ejb.parser.spec.ExtendingMetaDataParser.parse(ExtendingMetaDataParser.java:59)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossEjb3MetaDataParser.parseAssemblyDescriptor(JBossEjb3MetaDataParser.java:107)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossEjb3MetaDataParser.processElement(JBossEjb3MetaDataParser.java:148)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossEjb3MetaDataParser.processElement(JBossEjb3MetaDataParser.java:42)
	at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65)
	at org.jboss.metadata.ejb.parser.jboss.ejb3.JBossEjb3MetaDataParser.parse(JBossEjb3MetaDataParser.java:102)
	at org.jboss.metadata.ejb.test.common.UnmarshallingHelper.unmarshalJboss(UnmarshallingHelper.java:104)
	at org.jboss.metadata.ejb.test.common.UnmarshallingHelper.unmarshalJboss(UnmarshallingHelper.java:91)
	at org.jboss.metadata.ejb.test.common.UnmarshallingHelper.unmarshalJboss(UnmarshallingHelper.java:85)
	at org.jboss.metadata.ejb.test.bz1192591.IIOPParserTestCase.testIIOPWorkaround(IIOPParserTestCase.java:80)

https://github.com/jboss/metadata/pull/98

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

For what versions of EAP / Wildfly does this workaround actually work? Can we, for example, push the workaround to the eap7-quickstarts repository?

Created attachment 1237760 [details]
Screenshot of errors reported in duplicate bug 1193543

Released on 2017-09-05 as part of the EAP 6.4.17 release.