[
https://issues.apache.org/jira/browse/WSCOMMONS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656455#action_12656455
]
Benson Margulies commented on WSCOMMONS-377:
--------------------------------------------
The immediate problem in the initial report is that we have these 'schemas'
that have no content except for their imports. No TNS, no SystemID, no nuthin.
Long before the imports get into the act.
If the test case, which is simulating some product walking down the WSDL, gave
each one a unique system ID, all would be well. I'm going to ensure that this
is the case, and, if so, resolve this.
> XmlSchemaCollection does not handle multiple imports correctly
> --------------------------------------------------------------
>
> Key: WSCOMMONS-377
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-377
> Project: WS-Commons
> Issue Type: Bug
> Components: XmlSchema
> Reporter: Alexander Veit
> Priority: Blocker
> Attachments: wscommons-377.zip
>
>
> JAX-WS frequently generates WSDL files with the following schema import
> pattern:
> wsdl:
> {code:xml}
> <types>
> <xsd:schema>
> <xsd:import namespace="http://test.example.org/";
> schemaLocation="http://server/path/?xsd=1"; />
> </xsd:schema>
> <xsd:schema>
> <xsd:import namespace="http://jaxb.dev.java.net/array";
> schemaLocation="http://server/path/?xsd=2"; />
> </xsd:schema>
> </types>
> {code}
> xsd1:
> {code:xml}
> <xsd:schema xmlns:ns1="http://jaxb.dev.java.net/array";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; version="1.0"
> targetNamespace="http://test.example.org/";>
> <xsd:import namespace="http://jaxb.dev.java.net/array";
> schemaLocation="http://server/path/?xsd=2"; />
> <!-- element definitions -->
> </xsd:schema>
> {code}
> xsd2:
> {code:xml}
> <xsd:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; version="1.0"
> targetNamespace="http://jaxb.dev.java.net/array";>
> <!-- type definitions -->
> </xsd:schema>
> {code}
> XMLSchema cannot read both schema imports in the WSDL. It quits with
> org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
> collection. Namespace:
> at
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:139)
> at
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412)
> CXF-1624 is probably related to this bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
