Ruddi UDDI profiles

The UDDIProfile class of the "inspireit.uddi.request" package defines a context of execution for an UDDI client/server interaction. UDDIProfile is basically a set of name/value pairs that instruct the Ruddi runtime on how it has to behave.

The UDDIProfile mechanism is both a very simple and powerful mechanism. It allows a Ruddi developer to write a single piece of code that can be used within various contexts. For example, a first UDDIProfile could instruct the Ruddi runtime to connect to the Microsoft UBR using UDDI 2.0-compliant XML messaging and log the client/server interactions using Apache Log4J, while another could instruct the Ruddi runtime to connect to the IBM UBR using UDDI 1.0-compliant XML messaging and no logging.

The following lists the set of properties a Ruddi developer can use.

inspireit.uddi.inquiry.url :
Defines the URL to which UDDI inquiry requests have to be sent.
inspireit.uddi.publishing.url :
Defines the URL to which UDDI publishing requests have to be sent.
inspireit.uddi.publishing.username :
Defines the username part of the username/password combination to use to authenticate when publishing to a UDDI registry.
inspireit.uddi.publishing.password :
Defines the password part of the username/password combination to use to authenticate when publishing to a UDDI registry.
inspireit.uddi.version :
Defines the version of UDDI to use when connecting to the UDDI registry. The values should be one of "1.0", "2.0" or "3.0". The default is "1.0".
inspireit.uddi.logEnabled :
Defines whether logging is enabled. The value should be either "true" or "false". The default is "false".
inspireit.uddi.logging.provider :
Defines the logging system to use to log the XML messages exchanged between the UDDI client portion and the UDDI registry. The value is the name of the class implementing the logging system. If logging is enabled and no value is provided, logging information is written to System.out. Log4J can be used by providing the "inspireit.logging.Log4JLogger" value. An experimental XML-based logging system can be used by providing the "inspireit.uddi.logging.XMLLogger" value.
inspireit.uddi.transport :
Defines the transport implementation to use to connect to the UDDI registry. The value is the name of the class implementing the transport mechanism. Use "inspireit.uddi.transport.Axis10Transport" to use the Apache Axis 1.0 SOAP implementation instead of the default transport implementation of the library.

It has to be noticed that property names starting with "inspireit" are considered as reserved keywords. Trying to register a property with a name starting with "inspireit" and that is not a recognized reserved keyword will lead to the throwing of a runtime exception.

Also, it has to be noticed that System properties available at UDDIProfile creation time are automatically part of an UDDIProfile (the System properties can then evolve separately from the UDDIProfile ). It is hence possible to use System properties as a mechanism to define UDDIProfile globals. Remind that there are basically two methods to set System properties: via the setProperty() method of the java.lang.System class or via the command line when starting the application (cf. the -D option the Java Virtual Machine of SUN Microsystems).