So just looking at some configuration aspects (not implementation).... with the current http gateway (based on the embedded tomcat), you specify the listen address and port as part of defining a provider. Then on the bus definition, you specify the context e.g. <http-provider name="myhttp" host="localhost" port="9999"> | <http-bus busid="http1" context="/orders" /> | </http-provider> With the non embedded tomcat approach that we are proposing, a http bus will use the AS/ESB Server's http services and so there will be no configuring of the host and port. As already stated, the ESB deployment process will create a war sub deployment for the gateway. The gateway will then be deployed as with the normal war deployment process. So the provider/bus definition could be something as simple as: <http-provider name="http"> | <http-bus busid="orders" context="/orders" /> | </http-provider> Or just infer the context from the busid ala: <http-provider name="http"> | <http-bus busid="orders" /> | <http-bus busid="queries" /> | </http-provider> The listener config at the moment looks like this: <http-listener name="httplistener" busidref="orders" is-gateway="true" /> That works fine I think. One downside is that it seems to mean that we're restricted to a 1:1 bus:listener relationship for http. What if we added a "urlPattern" type config (mapping to the same in the web.xml) option on the listener (or provider perhaps?). That would allow a single bus to be used across multiple listeners e.g. <!-- "Dogs" order Service.... --> | <http-listener name="httplistener" busidref="orders" urlPattern="/dogs/*" is-gateway="true" /> | | <!-- "Cats" order Service.... --> | <http-listener name="httplistener" busidref="orders" urlPattern="/cats/*" is-gateway="true" /> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237948#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...