axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Oliver" <>
Subject RE: Document style web services
Date Sat, 23 Nov 2002 20:50:41 GMT
UDDI like most directory services is mostly useful for those that helped
design it.

The .NET Visual Studio use of UDDI is quite helpful when you are
developing consumer applications against published UDDI Web Services,
which I believe is the point.  Obviously if you are building a Web
Service and you are building the consumer application to interact with
the Web Service then UDDI doesn't make a lot of sense....I have seen
major companies use UDDI to provide a lookup of the internal Web Service
they restrict to their own applications....doe.  Further I know at least
one portal company that jury rigs a kludge UDDI to lookup the entry
point for a customer web service, only to use the UDDI to populate an
internal configuration value for the URL to the entry point....huh?  Why
force the customer to provide a UDDI to the customer's web service WSDL?
Doesn't the customer know the URL to the WSDL?

Michael Oliver
AppsAsPeers LLC
7391 S. Bullrider Ave.
Tucson, AZ 85747

-----Original Message-----
From: Dennis Sosnoski [] 
Sent: Saturday, November 23, 2002 12:52 PM
Subject: Re: Document style web services

Steve Loughran wrote:

>As an aside, does *anyone* use UDDI?
I'm personally really puzzled by the logic behind UDDI. As far as I can 
see there's a huge gap between the reality of what can be done using 
UDDI and the marketing concept behind it (which seems to be that you can

have your programs automatically look up and connect to services).

Where UDDI starts to make sense to me is when you have standardized 
interfaces to particular types of services - then the dynamic lookup and

use is actually possible. I don't know of any types of services that are

actually standardized in this manner, though. Perhaps ebXML is the 
missing piece of the puzzle here. Without interface standardization, 
simple web-page directories of services (such as XMethods and the like) 
seem far more useful than UDDI.

This is not knocking UDDI - I think it's a great tool, I just don't see 
any real use for it. :-) I'd love to be corrected on this if I'm 
overlooking something.

  - Dennis

Dennis M. Sosnoski
Enterprise Java, XML, and Web Services Support

View raw message