We're assuming that the Registry is available to both ESB-aware and ESB-unaware clients/services. (i) If ESB-unaware services want to register in it for use by ESB-unaware clients then the format they use for storing information is entirely up to them, i.e., we don't need to worry about it. (ii) if ESB-unaware services want to register for use by ESB-aware clients, then we obviously can't require that those services register EPRs because they are ESB-unaware. However, since our clients are ESB-aware, they'll expect EPRs to address those services, which means that the use of an external gateway is the way to go: the EPR addresses the gateway, which then translates the request message as well as redirecting the resulting message to the real service. (iii) if ESB-aware services want to register for use by ESB-unaware clients, then they publish their addresses as EPRs, since that's what ESB-aware services do naturally. We would develop a series of gateways to map EPRs to ESB-unaware address formats; these formats will typically be tied to the client's deployment environment (e.g., JEE or CORBA), so there will need to be a series of these adapters. (iv) if ESB-aware services want to register for use by ESB-aware clients, then they publish their addresses as EPRs and the clients use those EPRs. I think that just about covers it for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979199#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...