[jira] Assigned: (CXF-1229) Check for element name clash in request and response messages ignores setting of enableWrapperStyle

["Daniel Kulp (JIRA)" <ji...@apache.org>]

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

Daniel Kulp reassigned CXF-1229:
--------------------------------

    Assignee: Daniel Kulp

> Check for element name clash in request and response messages ignores setting of enableWrapperStyle
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CXF-1229
>                 URL: https://issues.apache.org/jira/browse/CXF-1229
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.0.2
>            Reporter: Christian Pfeifhofer
>            Assignee: Daniel Kulp
>             Fix For: 2.1
>
>         Attachments: test.zip
>
>
> One way to get around the method signature problems with a request and a response message having an element with the same name but with different datatypes is to disable wrapper style. wsdl2java (of CXF 2.0.2-incubator) ignores the setting of enableWrapperStyle and always fails to generate code in that case, reporting an error:
> WSDLToJava Error : Element
> {http://order.rbp.tmobile.at/services/rbpCheckDevices/}data has Having the
> same name with different
> types[{http://order.rbp.tmobile.at/datatypes}RbpCheckDevicesRequestDataType
> -- {http://order.rbp.tmobile.at/datatypes}RbpCheckDevicesResponseDataType],
> In wrapper style, there is a collision as per the spec.
> wsdl2java should check for enableWrapperStyle to be true (global and for a specific operation) before checking for name clashes in request and response messages and skip the check otherwise.

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