Back in 2004 the vendors wanted a "Google for web services". However they overlooked the contractual complexities between commercial entities that have to take place with human intervention before one company will consume the web service from another. So all thats really left as an application for UDDI is an intranet "endpoint directory" for which it is overkill.
Joined: Oct 07, 2005
Thanks to every one of you for your suggestions. I would like to know one more thing.
Do we really need to remember the tag names and attributes (which is mandatory/optional) mentioned in SOAP/WSDL/UDDI? The real exam expect us to do so?
Joined: Feb 05, 2004
You must understand
SOAP structure (part, envelope, header, body) faults: server, client, versionMismatch, mustUnderstand when these faults are throw.
WSDL types, portType, message, binding, service, you must know how each these items correspond in java code