cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Resolved: (CXF-1720) RPC/Lit soap 1.2 not processing the soap-rpc:result element
Date Thu, 24 Jul 2008 00:56:31 GMT


Daniel Kulp resolved CXF-1720.

    Resolution: Fixed

> RPC/Lit soap 1.2 not processing the soap-rpc:result element
> -----------------------------------------------------------
>                 Key: CXF-1720
>                 URL:
>             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
> 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.

View raw message