Registries and repositories

[marklittle]

There are actually two different aspects to the service bus: first, turning legacy systems and services into services that work within the SOA infrastructure; secondly, there is taking the services and adding policy and mediation control between those services. Integral to this is the notion of SOA Repositories: a repository is a persistent representation of an SOA Registry, which is needed to publish, discover and consume services. How registries/repositories are implemented is not important to the architecture: it's just another service after all. Example candidates would include UDDI implementations, or CORBA Trading Services. Therefore, the repository/registry needs to be in JBossESB from the start. Support for UDDI as one of the implementations will be included by default.

[anil.saldhana]

Starting jboss-4.0.2, we have an integrated UDDI v2 compliant UDDI registry included in JBoss. It is Apache juddi that is integrated. We also have a J2EE 1.4 certified JAXR stack in JBoss (also since jboss-4.0.2). So I suggest to leverage these, rather than creating fresh implementations.

http://wiki.jboss.org/wiki/Wiki.jsp?page=WS4EEJAXR

[marklittle]

We're definitely going to have UDDI support and not implement our own (except where necessary). So jUDDI is something we've been looking at as one of the UDDI implementations, but not necessarily the only one.

Mark.