| |

Introduction

Ruddi makes it easy to work with UDDI keys and implements the algorithms recommended by the UDDI 3.0 specification to convert UDDI 3.0-compliant keys to UDDI 2.0/1.0 UUIDs and inversely.

Quick reminder on UDDI 3.0, 2.0 and 1.0 keys formats

UDDI entities published in a registry such as a businessEntity, a businessService, a bindingTemplate or a tModel are uniquely labelled with a UDDI key. The format of an UDDI key varies depending on the version of UDDI used:

• UDDI 2.0 and 1.0 registries make use of UUIDs with the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
  For example, C1ACF26D-9672-4404-9D70-39B756E62AB4.
  
• UDDI 3.0 registries make use of URIs conforming to RFC2396.
  For example, uddi:uddi.org:categorization:types.

Ruddi UDDIKey notion and subclasses

In Ruddi, all UDDI keys, such as BusinessKey , EntityKey , ServiceKey , BindingKey and TModelKey , are sublasses of UDDIKey , a class of the "inspireit.uddi.base" package. UDDIKey defines methods allowing accessing the URI and UUID forms of a key:

• public java.net.URI getURI()
  Returns the URI corresponding to the UDDI key. If the UDDI key is an UDDI 3.0 key, already defined using an URI, it is returned "as is". Otherwise, the UDDI key is automatically converted in the URI form in compliance with the recommended UDDI key convertion algorithm defined in the UDDI 3.0 specification.
  
• public inspireit.uddi.util.UUID getUUID()
  Returns the UUID corresponding to the UDDI key. If the UDDI key is an UDDI 2.0 or 1.0 key, already defined using an UUID, it is returned "as is". Otherwise, the UDDI key is automatically converted in the UUID form in compliance with the recommended UDDI key convertion algorithm defined in the UDDI 3.0 specification.

Working with the KeysUtil class

Ruddi has a KeysUtil class in its "inspireit.uddi.util" package that makes it easy to determine whether an UDDI key is compliant with a given UDDI specification, or automatically convert it to the format defined in a given UDDI specification.

KeysUtil allows to:

1. Determine UDDI key compliance.
   Ruddi can determine whether an UDDI key is of the UDDI 3.0, 2.0 or 1.0 specification level thanks to a set of methods that return a boolean being given an UDDIKey to analyse.
   
2. Turn UDDI 2.0 and 1.0 keys to UDDI 3.0 keys.
   Ruddi can convert any UDDI 2.0 or 1.0 key to an UDDI 3.0-compliant format. To do so, Ruddi uses the recommended UDDI key convertion algorithm described in the UDDI 3.0 specification.
   
3. Turn UDDI 3.0 keys to UDDI 2.0 and 1.0 keys.
   Ruddi can convert any UDDI 3.0 key to an UDDI 2.0 or 1.0-compliant format. To do so, Ruddi uses the recommended UDDI key convertion algorithm described in the UDDI 3.0 specification.