[CXF-1769] Nillable schema elements in WSDL cause XmlSchemaException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.0.9, 2.1.3
• Component/s: JAX-WS Runtime
• Assignee: Daniel Kulp
• Reporter: John Hite
• Created: 28/Aug/08 15:35
• Updated: 15/Oct/08 04:52
• Resolved: 02/Sep/08 14:04

Description

A WSDL with a nillable schema element, e.g.

<element name="sayHelloResponse">
<complexType>
<sequence>
<element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
</sequence>
</complexType>
</element>

can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:

"org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"

Steps to reproduce:

1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.

If you remove the 'nillable="true"' from the wsdl, then this error goes away.