Creating Client Programs

Client programs can access the UDDI interface to Service Registry by using the SOAP 1.1 protocol over HTTP. Client programs in any programming language can access the UDDI interface service endpoint of Service Registry by using UDDI 3.0.2 Inquiry protocols. The endpoint for the UDDI Inquiry interface is as follows:

http://host:port/soar/uddi/inquire

The UDDI interface to the Service Registry conforms to the UDDI 3.0.2 Inquiry API WSDL as defined at the following URLs:

• UDDI API Binding: uddi_api_v3_binding.wsdl: http://uddi.org/wsdl/uddi_api_v3_binding.wsdl

• UDDI API Port Type: uddi_api_v3_portType.wsdl: http://uddi.org/wsdl/uddi_api_v3_portType.wsdl

You can develop a Java client program for the UDDI interface using JAX-RPC 1.1 by generating the client stubs from the previously listed UDDI 3.0.2 WSDL files. For details, see Chapter 8, “Building Web Services with JAX-RPC,” in the J2EE 1.4 Tutorial.

Additions and changes to the UDDI 3.0.2 WSDL and schemas to enable a Java client to be generated according to the requirements of the JAX-RPC 1.1 Specification are described in the UDDI Spec TC Technical Note at the following URL:http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-jax-rpc-20050126.htm.

The Java client program can then invoke methods on the UDDI Inquiry interface by using the methods exposed by the client stub.

In the current release of Service Registry, the UDDI interface does not support the UDDI 3.0.2 Publication, Security, Custody Transfer, or Subscription protocols. The following UDDI 3.0.2 interfaces are implemented to return E_unsupported (10050) error codes for every method:

http://host:port/soar/uddi/custody
http://host:port/soar/uddi/publish
http://host:port/soar/uddi/security
http://host:port/soar/uddi/subscription

The Inquiry interface implementation does not support authorization using -authInfo arguments or requests for partial results using either -listHead or -maxRows arguments.

Client programs that publish to the registry must use the JAXR API as described in earlier sections.