jUDDI (pronounced “Judy”) is an open source Java implementation of the Universal Description, Discovery, and Integration (UDDI) specification for Web Services.
- Open Source
- Platform Independent
- Supports for JDK 1.3.1 upto JDK 1.5
- UDDI version 2.0 compliant implementation
- Use with any relational database that supports ANSI standard SQL (MySQL, DB2, Sybase, JDataStore, HSQLDB, etc.)
- Deployable on any Java application server that supports the Servlet 2.3 specification (Jakarta Tomcat, JOnAS, WebSphere, WebLogic, Borland Enterprise Server, JRun, etc.)
- jUDDI registry supports a clustered deployment configuration.
- Easy integration with existing authentication systems
Ruddi is UDDI client library
UDDI client library implemented by Ruddi™ currently has the following characteristics:
- 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.
The OpenUDDI project is focused on creating a high performance, easy to use UDDI v3 compliant server and client library. The server and client is built using Java, version 5 for the server and version 1.4 for the client. The server uses Hibernate, and supports a wide variety of SQL databases, as well as LDAP for data storage.
The project is built on the Novell UDDI server but with many new features and optimizations.
SoapUDDI is an implementation of UDDI 2.0 compliant registry.
- Ready for deployment in private intranet environments.
- Conforms to UDDI 2.0 specifications.
- Written completely in JAVA.
- Persistence at the back-end using relational databases. Current release supports MS-Access, MS-SQL Server, Postgres and Sybase.
UDDI Browser is an open-source project that provides a friendly user interface allowing users to browse and manipulate content in UDDI registries. It is written in Java using the Swing libraries. Currently the browser supports version 2.0 UDDI registries.
The UDDI Browser supports the entire UDDI API for managing registries, including the whole query API set, and create/update/delete support for all entities in UDDI. It also has a host of features to make the UDDI users and administrators life easier, including query persistence, My UDDI support, and administrator utilities to aid in registry maintenance.
Apache Scout is an implementation of the JSR 93 – JavaTM API for XML Registries 1.0 (JAXR). Apache Scout has support for UDDI registries only and is heavily biased and tested with Apache jUDDI.
UDDI4J is a Java class library that provides an API to interact with a UDDI (Universal Description, Discovery and Integration) registry. The UDDI Project is a comprehensive, open industry initiative enabling businesses to (I) discover each other, and (II) define how they interact over the internet and share information in a global registry architecture. UDDI is the building block which will enable businesses to quickly, easily and dynamically find and transact with one another via their preferred applications.
UDDI::Lite is a library for UDDI clients in Perl.
Uddi4r is an open-source pure Ruby implementation of UDDI inquiry services. The project aims at providing Sevice-Oriented Architecture (SOA) support for Ruby and Rails applications. UDDI stands for Universal Description, Discovery and Integration; an OASIS standard commonly used for “yellow pages”-style querying and dynamic lookup of web services.
Popularity: 2% [?]