You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/10/28 21:36:59 UTC

[jira] Resolved: (CXF-1731) Unexpected control based on the namespace of the soap:body element

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

Daniel Kulp resolved CXF-1731.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3


This was fixed a long time ago.   I just ran the wsdl2java on the wsdl in that thread with and without the namespace in the soap:body and the generated code was identical.

> Unexpected control based on the namespace of the soap:body element
> ------------------------------------------------------------------
>
>                 Key: CXF-1731
>                 URL: https://issues.apache.org/jira/browse/CXF-1731
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.0.8
>            Reporter: Stéphane ARDOUIN
>             Fix For: 2.2.3
>
>
> It appears that CXF and/or JAXB interprets the attribute <soap:body namespace> of the WSDL as a control to apply on the namespace.
> For a schema without "elementForm=Qualified" elements, there shouldn't be such control. 
> This ticket is based on the thread "Different behaviors between Axis and CXF for namespaces" on 2008/07/29, ending with the following comment of Daniel Kulp :
> The namespace on the soap:body thing is really just used for Rpc/ 
> Lit.   In that case, the runtime needs to create a new wrapper element  
> which is the operation name plus that namespace.   For doc/lit which  
> everything is completely controlled by the elements in the namespace, it should be irrelevant.

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