| |

Introduction

Ruddi 1.0 provides many features, including the following:

• UDDI API for Java
• UDDI standards compliance
• UDDI Business Registry (UBR) Interoperability
• UDDI 3.0, 2.0 and 1.0 messaging
• UDDI-specific collection library
• UDDI-specific validation library
• Low-level interactions automation
• Extended query API
• Stream-based and RPC-based programming
• Multiple transport mechanisms
• Multiple logging mechanisms
• Easy installation
• Extensive documentation

Ruddi is an UDDI API for Java

Ruddi provides access to UDDI registries using an expressive pure Java API. No specific knowledge of XML, SOAP or UDDI messaging is required. Ruddi classes directly correspond to UDDI notions, making it easy for someone with UDDI skills to get started with Ruddi.

Ruddi is compliant with UDDI standards

Ruddi fully implements the publishing and inquiry UDDI APIs defined by the UDDI 3.0, 2.0 and 1.0 specifications available from www.uddi.org.

Ruddi interoperates with the UDDI Business Registry (UBR)

Ruddi has been tested for interoperability with the public Microsoft, SAP, NTT Communications and IBM UDDI Business Registries1.

Ruddi supports UDDI 3.0, 2.0 and 1.0 messaging

Ruddi transparently manages UDDI 3.0, 2.0 and 1.0 messaging. Ruddi objects are automatically serialized in an UDDI-compliant XML stream when connecting to an UDDI registry, and the replies are automatically deserialized in Ruddi objects.

The runtime uses either UDDI 3.0, 2.0 or 1.0 messaging to communicate with a UDDI registry depending on a user-defined profile. As a result, it is possible to write applications that can alternatively interrogate UDDI 3.0, 2.0 or 1.0 registries with no code change.

Ruddi comes with an UDDI-specific collections library

Ruddi comes with an UDDI-specific collections library allowing writing expressive, strongly typed UDDI applications.

Ruddi comes with an UDDI-specific validation library

Ruddi comes with a validation library allowing validating all UDDI data structures according to either the UDDI 2.0 or 1.0 specification (3.0 under development). For example, a business entity name of 150 characters will be detected as "too long" if the library is configured for validation again the UDDI 1.0 specification but will be considered valid if the library is configured for validation against the 2.0 specification.

Ruddi automates low-level interactions

Ruddi internally automates low-level UDDI interactions. For example, an authentication token will automatically be fetched using the appropriate information defined in a profile whenever a method of the publishing API is invoked.

Ruddi has an extended query API

Ruddi comes with an extended query API providing a higher-level of abstraction by hiding lower-level client/server interactions from the developer.

Ruddi supports stream-based and RPC-based programming

Ruddi allows accessing UDDI registry replies as streams that can be used for example as an input to an XSLT processor (for XML => HTML scenarios, for example).

Ruddi supports multiple transport mechanisms

Ruddi manages message transport internally or can delegate transport to the popular Apache Axis 1.0 SOAP engine.

Ruddi supports multiple logging mechanisms

Ruddi logging facility allowing monitoring the XML conversation between the UDDI client and the UDDI registry. System.out logging, as well as a Log4J-based and an experimental XML-based logging are supported.

Ruddi is easy to installation

Ruddi is easy to install. A Ruddi developer can get up to speed in less than five minutes.

Ruddi comes with extensive documentation

Ruddi comes with extensive documentation, including printable manuals in PDF, on-line Web pages, and Javadoc documentation.