OK.. if I am understanding your problem correctly, this could be simplified to the requirement that you want to expose your existing service under different WSDLs (using different namespaces) to different clients? If so, this is trivial in Synapse. You just create one or more proxy services with a publish WSDL specified to that which the client expects, and then forward the messages to the actual endpoint.
It seems like you might also need to write a mediator to change the namespace inside the SOAP messages in one case? In other words, presumably the namespace in the SOAP message matches in one case and doesn't in the other case. You can do this lots of ways, but the easy way would either be in XSLT or in JavaScript/E4X. If you can post an example of both types of SOAP message then I can show a transform that fixes up one. Unless I've completely misunderstood the problem in which case forgive me. Paul -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
