One customer requirement we've had related to this is to be able to dynamically provide the SoapProxy endpoint. Essentially, this would allow SoapProxy to be used as a load balancer. Here are two specific needs I've seen: 1.) Client is exposing a web service via the ESB that has 400 internal endpoints that the ESB can route to. Client is storing the endpoints in a registry and each endpoint has an associated "available" flag. Client wants the WS request to come to the ESB and then have the ESB route it (after potential authentication, authorization, transformation, auditing, etc.) to one of the "available" endpoints - where the list of "available" endpoints is not known when the ESB deployment is done (so can't be listed in jboss-esb.xml). 2.) Client is exposing a web service via the ESB that has 100 internal endpoints that the ESB can route to. Client is using JON, JMX, or some other mechanism to determine average response time of each internal endpoint and wants requests routed to less busy (defined by low response time) endpoints. I don't think the implementation of this has to be too complicated - don't think we necessarily need to make SoapProxy a complex load balancer. But, if SoapProxy could accept an endpoint that is passed into it as a parameter on the ESB message, that would allow clients to write a preceding action that used whatever mechanism they desired to determine where that particular message should be routed to by storing the desired endpoint in the ESB message prior to the SoapProxy action being executed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245605#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...