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 2008/07/24 02:36:31 UTC

[jira] Created: (CXF-1720) RPC/Lit soap 1.2 not processing the soap-rpc:result element

RPC/Lit soap 1.2 not processing the soap-rpc:result element
-----------------------------------------------------------

                 Key: CXF-1720
                 URL: https://issues.apache.org/jira/browse/CXF-1720
             Project: CXF
          Issue Type: Bug
          Components: Soap Binding
    Affects Versions: 2.0.7, 2.1.1
            Reporter: Daniel Kulp
            Assignee: Daniel Kulp
             Fix For: 2.1.2, 2.0.9


I was testing the CXF 2.1 client with SOAP 1.2.  I got an RPC-literal endpoint from the White Mesa server and had problems consuming it with the CXF client.  (I had no problems using soapUI.)  

Once the namespace issue was resolved, I got further, actually getting a response from the server.  However, the client threw an exception.  Using TCPMon, I observed that a response was received but the CXF client did not recognize the <result> element directly inside the operation response wrapper (See SOAP 1.2 Adjuncts). CXF is complaining that it finds no logical part that matches this element. 





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

[jira] Resolved: (CXF-1720) RPC/Lit soap 1.2 not processing the soap-rpc:result element

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.

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

Daniel Kulp resolved CXF-1720.
------------------------------

    Resolution: Fixed

> RPC/Lit soap 1.2 not processing the soap-rpc:result element
> -----------------------------------------------------------
>
>                 Key: CXF-1720
>                 URL: https://issues.apache.org/jira/browse/CXF-1720
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.1.1, 2.0.7
>            Reporter: Daniel Kulp
>            Assignee: Daniel Kulp
>             Fix For: 2.1.2, 2.0.9
>
>
> I was testing the CXF 2.1 client with SOAP 1.2.  I got an RPC-literal endpoint from the White Mesa server and had problems consuming it with the CXF client.  (I had no problems using soapUI.)  
> Once the namespace issue was resolved, I got further, actually getting a response from the server.  However, the client threw an exception.  Using TCPMon, I observed that a response was received but the CXF client did not recognize the <result> element directly inside the operation response wrapper (See SOAP 1.2 Adjuncts). CXF is complaining that it finds no logical part that matches this element. 

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