"tfennelly" wrote : &quot;mark.little(a)jboss.com&quot; wrote : "tfennelly" wrote : Couldn't the .esb name also be used as part of the local/global name e.g. "shopping-service.esb". We'd probably need to get the deployer to make it available somewhere, but that wouldn't be a big job. | | | | If we're looking to report on individual actions, then I'm not sure this will help. | | It would help because it's unique on a per AS/esb-service instance. It would help because it helps a reader of any report/log to narrow down to the .esb instance. Before you the service/listener/action name can mean anything, you surely need to know this (context). | | Then on a per .esb instance, the service/listener/action needs to be uniquely identified. OK, but this comes back to my question: what are we trying to identify? If it's *just* the Actions then we don't need this. If it's *just* the services then this helps. However, I think it should be *both* Actions and services (either together or individually). I'd have thought an Action should be identified within the scope of the service in some hierarchical manner. For example: : or <ESB instance>::<action type>:<action instance> The latter just in case we want to differentiate between multiple instances of the same Action within a service. If that's the case then what you mention would be the <ESB instance>, right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062323#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...