"tfennelly" wrote : 1. Allowing the context to be the bus specific part, defined on the bus (in the provider section) and allowing it to be whatever the user decides i.e. no artifical constraints/prefixes such as "http" etc. No, please keep the context as it is for now i.e. the name of the war file matching the esb deployment. "tfennelly" wrote : 2. Allowing the urlPattern to be a listener specific "filter" that filters certain requests off the bus (context) referenced by the listener's busrefid. Again, this can be whatever the user decides. We should certainly allow the user to specify the urlPattern provided that we make sure that there are no conflicts. Adding a prefix to the url is a simple and straight forward way to make sure that these never conflict with the EBWS. "tfennelly" wrote : In the case of EBWS, there wouldn't be an explicit bus or listener definition, so it's context and urlPattern could be something implied from the service definition e.g. context as "ebws" and listener urlPattern as "${service.category}/${service.name}" etc ? This is already how it works for EBWS, albeit without any prefix. Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245069#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...