WSDL Validation issue with wrapped style
----------------------------------------

                 Key: CXF-2024
                 URL: https://issues.apache.org/jira/browse/CXF-2024
             Project: CXF
          Issue Type: Bug
          Components: Tooling
            Reporter: Alexis Chemin
         Attachments: OrderDelivery.wsdl

I get a 'o.a.cxf.tools.common.ToolException' : "Element Party has Having the 
same name with different 
types[{http://www.orange.com/OrderDelivery}PartyViewRequest -- 
{http://www.orange.com/OrderDelivery}PartyViewResponse], In wrapper style, 
there is a collision as per the spec."
during the wsdl2java command when trying to generate code from a wrapped-styled 
WSDL, although the wsdl seems to be correctly built :
 
2 wrappers elements 'CreateParty' and 'CreatePartyResponse', each containing a 
single element 'Party' :
 
                  <element name="CreateParty">

                        <complexType>

                             <sequence>

                                   <element name="Party"

                                         type="tns:PartyViewRequest" />

                             </sequence>

                        </complexType>

                  </element>

                  

                  <element name="CreatePartyResponse">

                        <complexType>

                             <sequence>

                                   <element name="Party"

                                         type="tns:PartyViewResponse" />

                             </sequence>

                        </complexType>

                  </element>

 
 
The issue comes from the name of the element 'Party' which is the same within 
the 2 wrappers element, and obviously, if I change one of them to something 
else ('Party' to 'PartyResult') everything works ok. As the wsdl is generated, 
I can't really do this except for debugging purpose and I was wondering why cxf 
complains about this way of defining the wrapper elements ?

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

Reply via email to