jUDDI is an implementation of a UDDI v2 compliant registry service. You use it if you want to host your own registry.
UDDI4j is an implementation of a UDDI v2 compliant client API. You use it if you want to access a registry from a Java client application.
WSDL4J is an API for parsing WSDL.
SOAP toolkits, such as Apache Axis, typically supply a WSDL compiler (e.g., wsdl2java) that will parse the WSDL file and generate client code for accessing the service.
Anne
On 10/20/05, Desiree Hilbring <[EMAIL PROTECTED]> wrote:
-----Ursprüngliche Nachricht-----
Von: Pimjai Wesnarat [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 20. Oktober 2005 18:06
An: [email protected]
Betreff: Re: How to invoke a Web-Service and differences between jUDDI and UDDI4j
1.
jUDDI is a UDDI Registry.
UDDI4J is a library you can use to connect to UDDI Registry -- jUDDI or IBM Test UDDI or something else.
There're not the same thing.
Yes, so that means uddi4j is only helpful for one, who does not want to use his own registry and on the other side, if I do have jUDDI as as registry I do not need uddi4j at all, because the part covered by it is included in the jUDDI API as well, right?
Desiree
