You mentioned you have the SOAP target in the inbound message payload, so you could use an expression evaluator on the outbound-endpoint's address parameter to extract this and use it as the address.
Additionally, take a look at this:
http://www.mulesource.org/display/SAAJ/HomeIt includes a pair of transformers that might be more straightforward to deal with then stub classes.
Cheers,
-jd
bobs99 wrote:
Hi,
I am thinking of using Mule as a kind of centralized outbound SOAP gateway for many hosted applications, on several connected servers, all needing to make various external outbound SOAP requests.
The value of this is that certain aspects, like hosting security, can be more easily controlled than if each application managed its own outbound SOAP calls independently.
I'm wondering what's the most efficient way of setting this up in Mule when potentially large numbers (100+) of different external SOAP endpoints will be called?
The incoming events, from each hosted application, will be some XML containing the SOAP target URI, along with the operation and any parameters needed to make the call. I'm planning to use wsdl2java to generate all the client classes needed by CXF.
Although this is straightforward enough to get working with a few external SOAP endpoints, my main concern is how best to route the XML payload containing the operation and parameters, etc to the correct (out of potentially 100+) outbound CXF endpoint, both for best performance and without cluttering up the mule config file.
Is there a core Mule router to use or should I be thinking in terms of writing a custom router to achieve this?
Any advice (general or specific) on how to go about this would be welcome.
Thanks.
