|

Lesson 18: Working with the Apache Axis 1.0 SOAP implementation

Lesson objective

The objective of this lesson is to learn how to setup the Apache Axis 1.0 SOAP transport implementation.

Reference material

Source code of reference: Axis10Example.java

Related lessons

The Apache Axis 1.0 SOAP transport implementation can be used instead of the default transport implementation provided with Ruddi with all other lessons.

Review of concepts

The UDDI messages sent to or received from an UDDI registry are conveyed using the Simple Object Access Protocol (SOAP) that uses XML messaging over HTTP or HTTPS. Ruddi comes with a default SOAP implementation that doesn't make use of an external SOAP implementation mandatory. However, Ruddi allows plugging in the popular Apache Axis 1.0 SOAP implementation for use instead of the default implementation provided.

Code snippets

Transport is bound to the notion of UDDIProfile . We create a new UDDIProfile as follows:

UDDIProfile profile = new UDDIProfile();

We then enable Axis 1.0 SOAP transport by setting the inspireit.uddi.transport property to inspireit.uddi.transport.Axis10Transport :

profile.setProperty("inspireit.uddi.transport","inspireit.uddi.transport.Axis10Transport");

The UDDIProfile can be further configured depending on the needs of the application. For example, if the application is intended to lookup information in Microsoft's UBR, the inspireit.uddi.inquiry.url property needs to be setup appropriately:

profile.setProperty("inspireit.uddi.inquiry.url","http://uddi.microsoft.com/inquire");

If the application is intended to save information in Microsof's UBR, the inspireit.uddi.publishing.url property needs to be setup appropriately:

profile.setProperty("inspireit.uddi.publishing.url","https://uddi.microsoft.com/publish");

The UDDIProfile can then be used as described in the previous lessons on UDDI registry inquiry and publishing.

|

(c) INSPIRE IT, 2003 | Send us your feedback: developers@ruddi.biz