You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2011/08/15 14:25:27 UTC

[jira] [Created] (CAMEL-4336) camel-cxf payload should take consideration of the namespace which is defined in the soap envelope

camel-cxf payload should take consideration of the namespace which is defined in the soap envelope
--------------------------------------------------------------------------------------------------

                 Key: CAMEL-4336
                 URL: https://issues.apache.org/jira/browse/CAMEL-4336
             Project: Camel
          Issue Type: Improvement
          Components: camel-cxf
            Reporter: Willem Jiang
            Assignee: Willem Jiang
             Fix For: 2.9.0


Current camel-cxf PAYLOAD data formate can handle the namespace which is used as the element namespace, but it can not take consideration of namespace from soap envelope which is used in the attribute value likes xsi:type="xsd:String",
The soap envelop could be
{code}
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
       xmlns:ns1="http://cxf.component.camel.apache.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xmlns:ns2="http://cxf.component.camel.apache.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
       <soap:Body>
        <ns1:echo><ns2:arg0 xsi:type="xsd:string\">Hello World!</ns2:arg0></ns1:echo>
        </soap:Body></soap:Envelope>
    
{code}
The element in the PAYLOAD message body should be like this
{code}
<ns1:echo xmlns:ns1="http://cxf.component.camel.apache.org/" xmlns:ns2="http://cxf.component.camel.apache.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <ns2:arg0 xsi:type="xsd:string">Hello World!</ns2:arg0></ns1:echo>
{code}


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CAMEL-4336) camel-cxf payload should take consideration of the namespace which is defined in the soap envelope

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-4336.
---------------------------------

    Resolution: Fixed

Applied patch into trunk.

> camel-cxf payload should take consideration of the namespace which is defined in the soap envelope
> --------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4336
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4336
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.9.0
>
>
> Current camel-cxf PAYLOAD data formate can handle the namespace which is used as the element namespace, but it can not take consideration of namespace from soap envelope which is used in the attribute value likes xsi:type="xsd:String",
> The soap envelop could be
> {code}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>        xmlns:ns1="http://cxf.component.camel.apache.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>        xmlns:ns2="http://cxf.component.camel.apache.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>        <soap:Body>
>         <ns1:echo><ns2:arg0 xsi:type="xsd:string\">Hello World!</ns2:arg0></ns1:echo>
>         </soap:Body></soap:Envelope>
>     
> {code}
> The element in the PAYLOAD message body should be like this
> {code}
> <ns1:echo xmlns:ns1="http://cxf.component.camel.apache.org/" xmlns:ns2="http://cxf.component.camel.apache.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>   <ns2:arg0 xsi:type="xsd:string">Hello World!</ns2:arg0></ns1:echo>
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira