Getting Started with Ruddi - Ruddi interoperability

Introduction

Interoperability is key to the success of Web services. Ruddi has been carefully developed in order to be as compliant as possible with the various versions of the UDDI specification. Severe interoperability tests have been undertaken with the public Microsoft, SAP, NTT Communications and IBM UDDI Business Registries1. This section details the interoperability tests that have been performed in order to assess the Ruddi implementation.

UDDI 2.0 and 1.0 serializers and deserializers testing

Ruddi serializers and deserializers translating Ruddi objects to XML-based UDDI data structures and inversely have been tested by extracting several thousands of businessEntity and tModel data structures from the public UDDI registries and serializing them using Ruddi serializers. Then, the XML streams generated by Ruddi have been tested for equivalence with the original XML streams gathered from the UDDI registries. Each time the two XML streams where differing, the engineers of the Ruddi team have carefully verified "who was right" and adjusted the Ruddi implementation when needed. These tests have been performed for the four public UDDI registries, for both UDDI 2.0 and 1.0.

UDDI 3.0 serializers and deserializers testing

UDDI 3.0 serializers and deserializers are tested following the same philosophy as the UDDI 2.0 and 1.0 serializers and deserializers (read above). However, as far as UDDI 3.0 is not currently implemented by the public UDDI registries, the tests have had to be modified. This time, the XML streams generated by Ruddi are tested for compliance with the UDDI 3.0 XML schema only.

UDDI Publishing & other tests

Ruddi comes with about twenty sample applications illustrating many aspects of UDDI, such as publication and querying. These applications have all been run against the public UDDI registries, for both UDDI 2.0 and 1.02.

1. At the date of this writing (October 2002), only UDDI 2.0 and 1.0 could be tested as far as UDDI 3.0 is still not supported by the public nodes.

2. Except for the UDDI registry of NTT Communications. Registration is in Japanese only, and our request for assistance to test interoperability hasn't been encountered.