UDDI from Systinet Developer for Eclipse  Locate

Eclipse is an open source platform for tool integration. Systinet Developer for Eclipse, 5.5 extends the Eclipse IDE to support Web services creation, debugging, and deployment. Systinet Developer provides a simple point-and-click code generation experience that can turn any existing Java application into a Web service. Systinet Developer for Eclipse provides support for:

Getting Data from UDDI  Locate

UDDI searching wizards support the following use cases:

  • Retrieving a WSDL document from a UDDI registry into your project.

  • Creating Web service client applications from the WSDL document retrieved from a UDDI registry.

  • Creating Web service implementations from a WSDL document retrieved from a UDDI registry.

As you see, the core is to retrieve the WSDL document from a UDDI registry. Then, the WSDL document can be used for generating a Web service implementation or a Web service client.

You can obtain the WSDL file by the following methods:

  • You can get the WSDL file by WSDL service key or binding keys as shown in Figure 17. In this case, you must know exact UDDI keys. You can get these keys by searching a UDDI registry using a web interface. For searching BEA AquaLogic Service Registry, you can use both the Registry Console and the Business Service Console.

    BEA AquaLogic Service Registry is fully compliant with the latest UDDI Specification version 3. One of the benefits of the UDDI Specification version 3 is the option to use human readable UDDI keys. The first step of the UDDI inquiry wizard is selection of the version of UDDI Specification that you wish to use for accessing the UDDI registry. Systinet Developer for Eclipse 5.5 supports version 2 and version 3 of the UDDI Specification.

  • You can search by qualified names of the following sections of the WSDL definition:

    • WSDL portType (interface)

    • WSDL binding (transport)

    • WSDL service (endpoint)

    You can specify a target namespace for these qualified names as shown in Figure 18. You can also combine searching the UDDI registry with searching via BEA AquaLogic Service Registry Business Service Console that use names as interface, transport and endpoint for sections of a WSDL file.

Figure 17. UDDI Search by Keys

UDDI Search by Keys

Figure 18. UDDI Search by Qualified Names

UDDI Search by Qualified Names

Publishing WSDL to UDDI  Locate

UDDI publishing wizards allows you to publish the WSDL representing the Web service to a UDDI registry. The publishing wizard supports both version 2 and version 3 of the UDDI Specification. The selected WSDL file from your project will be published to the UDDI registry under the user account you provide in the publishing wizards as shown in Figure 19. Note that before you can publish a WSDL to a UDDI registry, you must create a business entity under which the WSDL definition representing the Web service will be published as shown in Figure 16.

Figure 19. UDDI Publish Wizard

UDDI Publish Wizard