[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

["John Hite (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment: HelloWorld.wsdl

The WSDL that causes problems

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: HelloWorld.wsdl
>
>
> 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"
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.