"dward" wrote : First, why can't ${service.category} be the context? This is done per esb deployment so there could easily be conflicts with other esb deployments (services in same category) or even other war deployments. "dward" wrote : Next, can you explain your reasoning why ebws and http paths must be kept separate? The only thing I can think of is if you wanted to provide *both* soap-ws/http and raw-xml/http access to the same service, at which point you'd have to distinguish them somehow. Someone could choose to do both, for whatever reason, and may even have multiple gateways pointing at the same target service. The EBWS is a fixed, 1-1 relationship but the http need not be. There could easily be different http gateways, with different composers and/or different security constraints, targeting the same ESB service. "dward" wrote : Last, what if ${service.category} and ${service.name} have spaces in them? The ESB allows for this, but my guess would be that for a url, each space would have to be replaced with %20. Just something to make sure we test. This is definitely something that we need to test, good point. Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245048#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...