That is certainly one approach and while, in theory, it may involve a little more configuration/code than other approaches (e.g. writing a template to transform/generate the SOAP payload), I would think it is easier to get working and to maintain afterwards. The "zero code" approaches are often cleaner in theory, but because there is "zero code", they usually involve a bit of black art re getting them to work.
Another approach might be to use one of the SOAPClient actions.
However, I am unable to get the HTTPRouter approach working completely due to ERROR:java.net.ConnectException: Connection refused: connect
Am using SoapUI to invoke the WS. If I point the url to the actual target service, it works just fine.
But if try to call the proxy service with the url as
http://<Server2>:8765//, it gives the connection refused error.
Both Server1 and Server2 can ping each other.
App server is running with -b 0.0.0.0 option.
Is something wrong or missing here?
But then are we really de-linking App A & B if we have to mention the target service name and not the proxy name when invoking from App A ?
As I continue to explore, hv a couple of questions"
1. In case of a Proxy Service on the bus using HTTPRouter, can the service act as proxy for more than one target webservices? How can it be achieved?
2. Can content based routing be used in above case which requires the action pipeline of 'RequestResponse' type?
If the message is routed to 2 destinations, response of which destination will be returned back to the caller?