Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.1, 2.0.7
-
None
Description
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.