cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <>
Subject [jira] [Commented] (CXF-5238) WSDL2Java generates naming conflicts on a valid schema
Date Thu, 29 Aug 2013 09:30:52 GMT


Freeman Fang commented on CXF-5238:


Could you please append the wsdl to reproduce this error?

> WSDL2Java generates naming conflicts on a valid schema
> ------------------------------------------------------
>                 Key: CXF-5238
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.7.5
>         Environment: Windows 7, Apache ant
>            Reporter: David Roytenberg
>              Labels: newbie
> When running wsdl2java on a valid WSDL, the tool reports naming conflicts under the following
> There is an element of this form
> <xs:element name="FooTransaction">
>   <xs:complexType>
>     <xs:sequence>
> 	<xs:element minOccurs="0"     name="request" nillable="true"							type="tns:FooTransactionRequest"
>     </xs:sequence>
>   </xs:complexType>
> </xs:element>
> and later another of the form 
> <xs:element name="FooTransactionRequest" nillable="true"
> 				type="tns:FooTransactionRequest" />
> Wsdl2Java reports a naming conflict 
> referencing the line numbers of the xs:element name="request and of the xs:element name="FooTransactionRequest"
> The validator in Eclipse says this is a valid WSDL.
> The service provider that owns the WSDL changed the inner element names inside the complex
types which created this problem.  The inner name used to be of the form "fooTransactionRequest"
which does not cause a problem.  In fact changing the name request to some other string also
fixes the name conflict.
> It looks like the inner element of the inner element is being appended to the name of
the outer element in the first block above, which generates a name identical to the element

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message