I think that when we agree on the structures, we can hide it all from the users. In fact we can probably define that right now. I think it will probably be something like this: | Class EPRRegistry { | | publish(String serviceName. EPR epr) | | Collection<Services> findServices(); | Collection<Services> findServices(String serviceType); | Collection<ServiceBindings> findServiceBindings(Service service); | ... more finders | | I'm assuming we will publish all Services under the same "JBossESB Organization". So we could hardcode that (or not..) We'll see, but this is what I was thinking of. I do think the user will usually get a collection of Services back, so he or she will have to decide which one to use, and then for that Service there may be multiple Bindings (each continaing an EPR), so again the user will have to figure out which one to use. Does that make sense? Or do you see clear rules on how to narrow down the results? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979654#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...