Discussions

News: Sun Announces a Service Registry product

  1. Sun Announces a Service Registry product (3 messages)

    Sun Microsystems announced a Service Registry product this week. The product is an integrated Registry and Repository based upon the OASIS ebXML Registry 3.0 standard and leverages the freebXML Registry open source project. In addition to the ebXML Registry 3.0 interfaces, it also supports a UDDI 3.0 Inquiry interface.

    The beta version of the product will be available as a free developer preview within the Java Web Services Developer's Pack 1.6 release this month. Final version will be available as part of Java Enterprise System 4 release later this year.

    The Server Side community members who will be at Java ONE 2005 are invited to stop by the booth #802 titled "Enabling Service-Oriented Architecture (SOA) With Service Registry" to get an in-depth look at Sun's Service Registry.

    Sun's Service Registry Web Site:
    http://www.sun.com/products/soa/registry/

    Press Release:
    http://www.sun.com/smi/Press/sunflash/2005-06/sunflash.20050615.1.html
  2. Congratulations Farrukh, and I'll be sure to stop by your booth at JavaOne. This should certainly help establish JAXR as a standard API for SOA registry repository.

    Miko
  3. Thanks Miko. Indeed as you point out this registry/repository implementation includes a complete JAXR Provider conformant with JAXR level 0 API profile.

    The JAXR Provider is used internally in the implementation by all clients of the registry/repository inclding the Web UI, Swing UI as well as the admin CLI client.

    Our experience confirms your statement about the value of JAXR as a standard API for SOA registry repository. It hides details of XML processing, SOAP 1.1/attachments communication as well as OASIS WSS based signing and verification of SOAP protocol messages using XML Digital Signatures.

    --
    Regards,
    Farrukh
  4. Indeed as you point out this registry/repository implementation includes a complete JAXR Provider conformant with JAXR level 0 API profile.

    Above statement has a typo. The JAXR provider is a level 1 provider with support for the complete JAXR API (level 0 + level 1).

    I meant to say the following:

    "
    Indeed as you point out this registry/repository implementation includes a complete JAXR Provider conformant with JAXR level 1 API profile.
    "

    Thanks.