"Kevin.Conner(a)jboss.com" wrote : "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. I don't see why having multiple services in the same category would cause a problem. Brainstorm: - new ${service.category} + new ${service.name} = deploy a new war with ${service.category} as the context, which contains a servlet which dynamically routes the request to the appropriate ESB service (via ServiceInvoker) based on parsing the uri path for ${service.name}. - existing ${service.category} + new ${service.name} = no deployment change necessary because the servlet will dynamically route based on the new ${service.name} - existing ${service.category} + remove ${service.name} = no deployment change necessary, *unless* there are no more ${service.name}'s associated with that ${service.category}, at which point the context (webapp) is undeployed. Concerning "other war deployments", this will always be an issue no matter what we do. Even if we come up with a single context name that sounds very ESB-specific, there's still the chance someone could have named their war that, too. We just have to have a warning in the documentation about this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245055#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...