This is extremely strange. I have no idea what would cause that. :-( And
not having a windows box, not really something I can debug. Can I ask for
some help from you in debugging this or at least coming up with a reproducible
case?
1) Is there any way you could test it without the WS-Security stuff? Maybe
the soap header stuff is causing a confusion. I doubt it.
2) Can you create a small "hello world" cxf server (or take our samples) and
make it soap 1.2 and see if a .NET client for that exibits the same thing.
If so, can you file a JIRA with the modified sample and a "raw" capture of the
.NET message off the wire if at all possible. Even better if you could
create a small "main" method client that just uses an HTTPUrlConnection to
post the exact message (and headers) to see if the response is still 1.1 from
that.
Dan
On Thu February 4 2010 6:01:28 pm huidong wrote:
> I am running CXF 2.2.6 on the server side, with soap binding set to 1.2
>
> <jaxws:binding>
> <soap:soapBinding version="1.2"/>
> </jaxws:binding>
>
> for java client, if the incoming request is soap1.1, the response is 1.1;
> same for 1.2. everything works fine. However, for .Net basicHttpBinding
> client, the incoming request is soap1.1, but the response from CXF is set
> to 1.2. this caused .Net client refused to take it.
>
> incoming:
>
> [14:35:05.586] {http--81-10$149817582}
> --------------------------------------
> [14:35:31.592] {http--81-9$2096725241} Inbound Message
> [14:35:31.592] {http--81-9$2096725241} ----------------------------
> [14:35:31.592] {http--81-9$2096725241} ID: 10
> [14:35:31.592] {http--81-9$2096725241} Address:
> /saw/services/SawSelfServices
> [14:35:31.592] {http--81-9$2096725241} Encoding: UTF-8
> [14:35:31.592] {http--81-9$2096725241} Content-Type: text/xml;
> charset=utf-8
>
> [14:35:31.592] {http--81-9$2096725241} Payload: <s:Envelope
> xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity
> -utility-1.0.xsd"><s:Header><o:Security s:mustUnderstand="1"
> xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity
> -secext-1.0.xsd"><o:UsernameToken
> u:Id="uuid-7e53a9b5-368b-4766-a014-9eb130cd0ab9-1"><o:Username>ws</o:Usern
> ame><o:Password
> o:Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
> oken-profile-1.0#PasswordText">***</o:Password></o:UsernameToken></o:Securi
> ty></s:Header><s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>***</s:Body></s:Envelope>
> [14:35:31.592] {http--81-9$2096725241}
> --------------------------------------
>
> outgoing response:
>
> [14:35:31.629] {http--81-9$2096725241} Outbound Message
> [14:35:31.629] {http--81-9$2096725241} ---------------------------
> [14:35:31.629] {http--81-9$2096725241} ID: 10
> [14:35:31.629] {http--81-9$2096725241} Encoding: UTF-8
> [14:35:31.629] {http--81-9$2096725241} Content-Type: application/soap+xml
> [14:35:31.629] {http--81-9$2096725241} Headers: {}
> [14:35:31.629] {http--81-9$2096725241} Payload: <soap:Envelope
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope";><soap:Body><forgetUser
> IdResponse
> xmlns="http://secureaccess.wa.gov/";>***</soap:Body></soap:Envelope>
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
