mattrpav wrote: > > If you just want processes within ServiceMix to have access to the web > services, than just deploy the service-engine side of things and do not > expose the binding component. > > >
How to do that was my initial question, in a sense. I want Servicemix to act as a gateway and proxy the webservices. The client shouldn't even know what's happening behind the curtain. Something like this (ignore the "firewall"): http://www.nabble.com/file/p17236372/fig1.gif The client can see a WSDL file and send SOAP messages to the endpoint defined in it. But that "WSDL for Export" should be a dynamically created replicate of the real WSDL file, which can be anywhere. How could I achieve this setup with servicemix? -- View this message in context: http://www.nabble.com/Servicemix-as-single-access-point-to-several-web-services-tp17129303p17236372.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
