The WSDL didn't make it through the apache filters.  :-(

That said, any chance you could try the latest 2.1.4 snapshot:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-cxf/ 

I fixed some issues in this area fairly recently so it MAY be fixed.   If not, 
feel
free to log a JIRA and attach the wsdl there.

Thanks!
Dan





On Tue February 3 2009 8:42:39 am [email protected] wrote:
> Hi,
>
> 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 ?
>
> From my point of view, the 2 wrappers elements are named differently, so
> i don't know what kind of proplem could occur at runtime (no ambiguity).
> I was expecting a generated code like this :
>
>     @ResponseWrapper(localName = "CreatePartyResponse", targetNamespace
> = "http://www.orange.com/OrderDelivery";, className =
> "com.orange.orderdelivery.CreatePartyResponse")
>
>     @RequestWrapper(localName = "CreateParty", targetNamespace =
> "http://www.orange.com/OrderDelivery";, className =
> "com.orange.orderdelivery.CreateParty")
>
>     @WebResult(name = "Party", targetNamespace = "")
>
>     @WebMethod(operationName = "CreateParty")
>
>     public com.orange.orderdelivery.PartyViewResponse createParty(
>
>         @WebParam(name = "Party", targetNamespace = "")
>
>         com.orange.orderdelivery.PartyViewRequest party
>
>     );
>
>
>
> could it be somehow related to CXF-918 or CXF-1229 entries ?
>
> cxf used : cxf-2.1.2
> please find the full wsdl attached.
>
> Thanks for any help
>
> Alexis Chemin
>
>
>
>
> *********************************
> This message and any attachments (the "message") are confidential and
> intended solely for the addressees. Any unauthorised use or dissemination
> is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered,
> changed or falsified. If you are not the intended addressee of this
> message, please cancel it immediately and inform the sender.
> ********************************

-- 
Daniel Kulp
[email protected]
http://www.dankulp.com/blog

Reply via email to