"tfennelly" wrote : I think what you're missing is the difference between the actions "name" and "class". One should be allowed to have multiple action instances having the same "class" attribute value on a single action pipeline, but each of these must have a unique "name" for that chain e.g. in the following action chain, we have 2 transformers with the same "class", but different "name"s. The "name" is what we could use in the global version of this actions name. Yes, I'd forgotten about the name in the xml config. That makes it easier to do the class name/instance name automatically. "tfennelly" wrote : Right, but I think it only needs to be unique on a per service/action-chain basis, right? You should be able to have the same action on 2 different chains e.g. "transform_CSV2XML" on 2 different action chains within the same dot esb. Globally, they'd be qualified by their containing service category+service name, which would be unique within the scope of the .esb (right?). | | Yeah, so we need to enforce uniqueness wherever we need to. However, I think we need to be careful about making statements concerning *global uniqueness* based on service category and service name when we don't have a formal policy for federated registries yet. So it sounds like we have the information for uniqueness within an ESB deployment that we covered earlier today. So now do we go back to the issue of nicknames ;-)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062654#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...