cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: cxf client for non ws-i bp compliant services?
Date Mon, 29 Oct 2007 19:01:20 GMT


What version of CXF are you using?

At one point (don't remember when) I did update the RPCInInterceptor to 
only compare local names and ignore the namespace to workaround issues 
with non WS-I BP compliant services.  The messages CXF generates are 
always WS-I BP compliant, but it should be able to process the 
non-compliant messages as well.     I THINK that made it into 2.0.2, but 
it might not have made it so would be in 2.0.3.   Can you check the 
2.0.3 SNAPSHOT version and see if that works?


On Thursday 25 October 2007, Christian Vest Hansen wrote:
> I have an XFire 1.2.6 web service that I wan't to write a CXF client
> for, but when I invoke operations on this service CXF throws
> exceptions with messages like "Found element
> {}vats but could not find matching RPC/Literal
> part" - this is because the XFire web service dosn't comply with the
> WS-I Basic Profile, and qualifies the SOAP response message parts with
> a namespace when it shouldn't.
> Is there any way to lax the CXF strictness? I'de prefer it if I didn't
> have to touch the XFire code, but if that's the only way to go about
> this then I'de still like to hear any proposed solutions.
> Otherwise I see two other options:
> + scrap CXF for this particular service and do a HttpClient + StAX
> type of client, or..
> + convince the project manager that now is the right time to port the
> service in question (which is unlikely)

J. Daniel Kulp
Principal Engineer
P: 781-902-8727    C: 508-380-7194

View raw message