Hi Johannes,
I'm not sure I understand what you want.
Do you mean you want publish wsdl with ns version3, and you use client
with ns version1, and you hope ns version1 client can talk with ns
version3 server?
If so, I'm fear you can't do that.
I don't know what's your wsdl looks like, so I can't tell your soap
message type, such as rpc/literal or doc/literal/wrapped. For
rpc/literal, since the message part is not qualified, which means only
localName is used, so it may work across different ns version. But it's
definitely not working for doc/literal which element is qualified so we
need the match namespace to find operation from servicemodel.
You mentioned "This works fine on the original service, but the
cxf-bc-service faults with an "operation not bound"-exception", I can't
understand it, what's the origianl service, it's also by cxf?
Regards
Freeman
Johannes Elsinghorst wrote:
Hi,
i have a ws that supports different clientversions. It does this by
accepting different namespaces in the soapmessage like this:
<envelope xmlns ns0="http://ws/version1";>
...
</Envelope>
<envelope xmlns ns0="http://ws/version2";>
...
</Envelope>
<envelope xmlns ns0="http://ws/version3";>
...
</Envelope>
I have this WS in lets say version3 and use its wsdl to publish it on
the bus via cxf.
For interoperability across versions the client tries to invoke
operations on the ws using the version1-ns.
This works fine on the original service, but the cxf-bc-service faults
with an "operation not bound"-exception,
since in its wsdl the version3-ns is used.
Is there any solution to this?
Thanks, Johannes
