Features
Examples
Manuals
Javadoc
Articles
FAQ
Mailing lists
Downloads
Known bugs
Sub-Projects
Useful Links
License
Pricing
Contacts
Legal
- Ruddi™ provides access to UDDI registries using an expressive pure Java API. No specific knowledge of XML, SOAP or UDDI messaging is required.
- Ruddi™ fully implements the publishing and inquiry UDDI APIs of UDDI V3, V2 and V1.
- Ruddi™ has a tested interoperability with the public Microsoft, SAP and IBM UDDI Business Registries (UDDI V2 and V1 only, as far as V3 is not currently implemented by the public nodes).
- Ruddi™ transparently manages UDDI V3, V2 and V1 messaging. The runtime uses either UDDI V3, V2 or V1 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 V3, V2 or V1 registries with no code change.
- Ruddi™ has UDDI-specific collections library allowing writing expressive, strongly typed UDDI applications.
- Ruddi™ has a validation library allowing validating all UDDI data structures according to either the UDDI V2 or V1 specification (V3 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 V1 specification but will be considered valid if the library is configured for validation against the V2 specification.
- 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 providing a level of interaction equivalent to what JAXR proposes.
- 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™'s message transport can be managed internally or be delegated to the Apache Axis V1 SOAP engine.
- Ruddi™ has a 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 install. Get up to speed in less than 5 minutes. Learn by example with the about 20 examples provided with the library.
- Ruddi™ has extensive documentation.
Support us!
Buy documentation
Buy licenses
Donate
Ruddi™ is open source software
