[jira] Commented: (CXF-1123) ClientFaultConverter needs to deal with unqualified part names.

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

    [ https://issues.apache.org/jira/browse/CXF-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536262 ] 

Daniel Kulp commented on CXF-1123:
----------------------------------


However, the WS-BP also specifically says:  (section 4.4.2)

R2205 A wsdl:binding in a DESCRIPTION MUST refer, in each of its soapbind:header, soapbind:headerfault and soapbind:fault elements, only to wsdl:part element(s) that have been defined using the element attribute.

and:

Because faults and headers do not contain parameters, soapbind:fault, soapbind:header and soapbind:headerfault assume, per WSDL 1.1, that the value of the style attribute is "document". R2204 requires that all wsdl:part elements with a style attribute whose value is "document" that are bound to soapbind:body be defined using the element attribute. This requirement does the same for soapbind:fault, soapbind:header and soapbind:headerfault elements.


Thus, Faults (and headers, BTW) are always in Doc/Literal form and thus should be properly qualified.    The RPC/Lit rules do not come into play for the Faults.


That all said, is there a specific test or wsdl or service or something that is not working due to this?   If there is a service not sending faults back properly qualified, that would be a bug in that service.






> ClientFaultConverter needs to deal with unqualified part names.
> ---------------------------------------------------------------
>
>                 Key: CXF-1123
>                 URL: https://issues.apache.org/jira/browse/CXF-1123
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.2
>            Reporter: Jose Garcia-Sacristan
>             Fix For: 2.0.3
>
>
>  WSI-BP states that RPC/Lit part accessors should be completely unqualified. ClientFaultConverter needs to support this.
>                

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