Hi,
I can't understand why you need change namespace in wsdl.
If you generate client code stub using wsdl2java from different
wsdls , then the client code will generate soap message with correct
namespace by default, IMO you needn't worry it at all.
Anyway, you can always use customer interceptors on client side to
modify In/Out message namespace whatever you want, here is an
example[1] to demonstrate how to do it with In message, but this will
break the stream way to process the message so it will impact the
performance.
[1]https://svn.apache.org/repos/asf/servicemix/components/trunk/bindings/servicemix-cxf-bc/src/test/java/org/apache/servicemix/cxfbc/interceptors/NamespaceMoveInterceptor.java
Freeman
On 2011-12-14, at 上午4:20, Rahul Somasunderam wrote:
Hi,
I'm working on a health project. There are a bunch of standards that
we use that are available to us as a WSDL.
The WSDLs are located at ftp://ftp.ihe.net/TF_Implementation_Material/ITI/wsdl/
However different implementors serve the WSDL with different
namespaces in the WSDL. And this seems to make it hard for me to
integrate with any random implementor.
For instance, this is my own server using CXF -
http://107.20.211.185/hd/services/xdsregistryb?wsdl
This is NIST implementing the same using Axis2 -
http://ihexds.nist.gov:9080/tf6/services/xdsregistryb
I've created a testcase that shows how my CXF client code fails.
<cxf-testcase.zip>
How am I to deal with changing namespaces in WSDLs?
R,
rahul
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
