Dennis, I agree that the original design concept for UDDI -- a single global registry of services that would enable dynamic discovery of business partners -- was just a bit far fetched. In fact, the idea of using UDDI as the primary means of service discovery within an organization is a bit far fetched. But UDDI does play a very important role in a SOA runtime infrastructure, which is an ecosystem of cooperating products (service platforms, mediation systems, and management systems) that need a way to exchange information about services. UDDI is not perfect, and I'd like to see someone propose additional APIs to augment SOAP, but it does provide a standard system of record for the environment and a standard means to retrieve information about service.
As I said, UDDI makes an incredibly poor repository to support development time discovery and governance. It simply doesn't contain enough information about services and service artifacts, and the data model organization is just wrong to support development activities. (I will note, though, that all IDEs have a built-in UDDI browsing capability.) I recommend using a repository to support development time activities, and maintain the registry to support the runtime system of record capability. Note that the leading registry/repository vendors (HP/Systinet, Software AG/Infravio, BEA, and IBM) have either extended UDDI with repository features (Software AG) or they offer a separate repository that synchronizes with the UDDI registry (the others). The HP/Systinet repository sounds somewhat similar to Paul's project. It is an entirely REST-based repository. I find it interesting that Systinet found it necessary to define a Java API to abstract the REST API to make it more palatable to the average enterprise developer. (Paul -- I suggest you confer with Radovan on your API.) Anne On Dec 8, 2007 11:22 PM, Dennis Sosnoski <[EMAIL PROTECTED]> wrote: > Hi Paul, > > Great to see this! It's something that I've thought was needed for a > long time. UDDI was designed for a world that doesn't now exist, and is > unlikely to develop within our lifetimes, where AI-type applications are > able to analyze services based on simple descriptions and link them > together at runtime to fulfill user needs (via liberal application of > magic pixie dust). It's a shame that it was blessed as a Java standard > by the Sun process when it had so little in the way of useful > functionality, but I think that's just due to the political nature of > the standardization process. > > It'll be great when WSO2 gets out some user documentation (or even > architecture documents) for the project. I'm personally not big on > looking through source code to deduce where a project is going, but I > heartily approve of the goals. > > - Dennis > > -- > Dennis M. Sosnoski > SOA and Web Services in Java > Axis2 Training and Consulting > http://www.sosnoski.com - http://www.sosnoski.co.nz > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 > > > > Paul Fremantle wrote: > > You might want to look at the project being built here - its about > > using lightweight REST models to build a registry instead of UDDI. > > > > http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html > > <http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html> > > > > Paul > > > > On Dec 7, 2007 2:43 AM, <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Hello, > > > > Is anyone out there using a UDDI registry for their services? I'm > > considering a registry for our loose bundling of web services, > > but we > > only have a handful of services in play. I am not sure if a > > registry is > > overkill given our setup. > > > > I started looking at UDDI this afternoon when I got fed up with adding > > wsdl (and related schema) to my BPEL partner link definitions. > > JDeveloper > > offers the ability to point to a UDDI registry to "discover" wsdl for > > partner links. > > > > Thanks, > > > > Alejandro > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > -- > > Paul Fremantle > > Co-Founder and VP of Technical Sales, WSO2 > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > "Oxygenating the Web Service Platform", www.wso2.com > > <http://www.wso2.com> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
