cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sosnoski (JIRA)" <>
Subject [jira] Commented: (CXF-1254) WS-A Interop with .Net WCF - CXF fails to interop with .Net WS-A due to use of old namespace.
Date Mon, 24 Jan 2011 23:01:54 GMT


Dennis Sosnoski commented on CXF-1254:

Metro also uses the official WS-A 2005/08 with WS-RM 1.0. I agree that this contradicts the
WS-RM 1.0 spec, but it looks like everyone else has standardized on this variation.

I'd suggest either changing the default for the client to WS-A 2005/08 with an option to override
for the older namespace, or keep the default the same and give an option to use 2005/08. I
think the server should adapt to whatever namespace is used by the client, as with other parts
of CXF.

> WS-A Interop with .Net WCF - CXF fails to interop with .Net WS-A due to use of old namespace.
> ---------------------------------------------------------------------------------------------
>                 Key: CXF-1254
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.0.3
>         Environment: CXF 2.0.3
> JBoss
> Spring
> .Net WCF client
> WSDL first development
>            Reporter: Paul Freeman
> CXF is not compatible with .net's WCF implementation.  I have successfully configured
reliable messaging in both CXF and .net.  The client is .net and the service is CXF.  .net
makes the initial request to create a sequence and expects the response to contain a <RelatesTo>
header tag.  The namespace for this header tag is an addressing namespace.
> It turns out that CXF returns the addressing namespace
> But WCF sent the request with the this namespace:
> So the result is that WCF cannot find the <RelatesTo> header tag.  
> I wrote the wsdl with this namespace, which is all together different as well:
> Here is the entire message exchange captured by wireshark:
> ==========================================================
> POST /saas-identity-2.0-CXF-WSDLFirst/services/IdentityService HTTP/1.1
> Content-Type: text/xml; charset=utf-8
> SOAPAction: ""
> Host: ad1vm-saasdev
> Content-Length: 695
> Expect: 100-continue
> Connection: Keep-Alive
> HTTP/1.1 100 Continue
> <s:Envelope xmlns:s="" xmlns:a=""><s:Header><a:Action
200 OK
> Date: Fri, 30 Nov 2007 16:42:27 GMT
> Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET
> X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5
> SOAPAction: ""
> Content-Type: text/xml;charset=utf-8
> Content-Length: 538
> <soap:Envelope xmlns:soap=""><soap:Header><MessageID
xmlns="" RelationshipType="reply">urn:uuid:c211d39e-e26b-4345-8c4a-a5c931ec210d</RelatesTo><Action
> ==========================================================
> A "patch" for this issue already exists in JIRA - but it doesn't seem to work.  Looking
at the code around the patch, there are explicit calls to classes in the
> The class in question is org/apache/cxf/ws/addressing/
> It is located in \rt\ws\addr\src\main\java
> It uses many classes in the package to construct
the returned objects.  This should really be upgraded to a newer namespace.
> In order to be compatible with WCF, the new namespace for addressing should be at a minimum:
> I am sure the fix will entail upgrading the package of classes found in:

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

View raw message