[jboss-dev-forums] [Design of JBoss ESB] - Re: How to store EPRs in the registry?

[mark.little@jboss.com]

"kurt.stam at jboss.com" wrote : 1. Gateways, ESB-unaware services - Gateways can be used by non-ESB aware clients/services to access ESB services. The addresses for these gateways can be arbitrary and shouldn't be influenced by the EPR. It seems logical to use a URI to define such and endpoint and we can store URI's in the registry (the ServiceBinding contains a URI-element)
  | 

The gateway concept is still under development, so I'd prefer to postpone any discussion on this until we've got that completed. Otherwise it's potentially like shooting at a moving target.

anonymous wrote : 
  | 2. ESB-aware services. ESB-aware services have a fully populated EPR and all of this information can no longer be stored in an URI. The current thinking is to store the entire XMLized EPR to the registry.
  | 

That approach has precedent with Web Services.

anonymous wrote : 
  | To store WSDL the tModel is used (in JAXR this is a Concept(fingerprint) and/or Classification(namespace), see also http://java.sun.com/developer/technicalArticles/WebServices/jaxrws/
  | 

We'll certainly need to store WSDL and other contract definition information later, as we really explode how the ESB uses the Registry. At the moment we're really looking at the first steps though: more like a basic naming service. So I wouldn't expect we're looking at anything more complex than an EPR. Would you?

anonymous wrote : 
  | . We may want to store the EPR-XML in the same place. If we do so, what will we put in the URI reference for the ServiceBinding. Maybe something like "epr://jbossesb" to define what type of 'protocol' we are using.
  | 
  | Well I hope this is enough to start a discussion on this matter.
  | 
  | --Kurt

Is this not where the Logical Name comes in? From the outset we've talked about two types of names:

(i) the "physical" name, which is the EPR and needed to address the service. This name may be obtained from the Registry or from elsewhere. But the Registry is the preferred approach.

(ii) the "logical" name, which is a convenient short-hand, like "Kurt's Travel Agency". Obviously in order to interact with a service you need a real address, so if all you've got is a logical name you need some way of mapping one to the other. That's where the Registry comes in again. The Registry maintains a tuple space of <logical name, physical name>.

We could set the logical name as the URI. As you say, something like: epr:jbossesb:version:1.0:logicalname:KurtsTravelAgency

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979203#3979203

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979203