cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Resolved: (CXF-2166) Incorrect namespace in SOAP
Date Mon, 05 Oct 2009 16:54:31 GMT


Daniel Kulp resolved CXF-2166.

       Resolution: Incomplete
    Fix Version/s: Invalid

Request for more information is unanswered for 6 months.  

> Incorrect namespace in SOAP
> ---------------------------
>                 Key: CXF-2166
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.2
>         Environment: CXF 2.2
>            Reporter: Oscar Reitsma
>             Fix For: Invalid
> There appears to be a bug with the generation of SOAP messages.
>  I am using a Java CXF 2.2 client to consume a WCF service with basic-http binding. I
used wsdl2java to generate the proxy objects.
> I am getting the error below:
>  Error in line 1 position 1361. 'EndElement' 'request' from namespace ''
is not expected. Expecting element 'MyMember2'.</Message><StackTrace>   at System.Runtime.Serialization.XmlObjectSerializerReadContext.ThrowRequiredMemberMissingException(XmlReaderDelegator
xmlReader, Int32 memberIndex, Int32 requiredIndex, XmlDictionaryString[] memberNames)&#xD;
>  I think I have narrowed the issue down to the incorrect namespace being referenced in
the soap message that is being generated:
> The outbound message is as follows:
> <soap:Envelope xmlns:soap=""><soap:Body><MyMethodCall
xmlns="" xmlns:ns2="http://MyNS1" xmlns:ns3=""
xmlns:ns4="" xmlns:ns5=""
xmlns:ns6="" xmlns:ns7=""
xmlns:ns8="" xmlns:ns9="">
> <request>
>     <ns3:MyMember1>9736399</ns3:MyMember1>
>     <ns4:MyMember2>
>         <ns4:MyMember3>false</ns4:MyMember3>
>     </ns4:MyMember2>
> </request>
> </MyMethodCall>
> </soap:Body>
> </soap:Envelope>
> MyMember2 can actually be found in the namespace ns3, and not ns4 as indicated by the
SOAP message. I used fiddler2 to change the sent SOAP message to use the ns3 namespace, instead
of ns4. After this change the call was made successfully.
>  The proxy object generated by wsdl2java appears to have been generated correctly, and
references the correct namespace.
>  Has anyone seen this problem before, or am I missing something rather obvious?
>  Kind Regards,
> Oscar

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

View raw message