I'm sorry, but a list of <20 companies that have adopted ebXML Registry five years after the specification was ratified as a standard is not an indication of success. ebXML Registry's only major vendor proponent (Sun) has recently withdrawn its support. (Sun's ebXML Registry product is now in maintenance mode.) From a market perspective, ebXML Registry is dead.
As for webMethods Infravio X-Registry -- If you look at the Infravio product information, it doesn't even mention ebXML. Infravio uses a data model based on the JAXR specification (which supports both UDDI and ebXML). It is fully UDDI v3 compliant. It also supports the JAXR Level 1 API (designed to work with ebXML v2 registries), but it does not directly support the ebXML SOAP APIs. It is not ebXML compliant. Anne On 2/7/07, Jason Baragry <[EMAIL PROTECTED]> wrote:
Those looking for an alternative take on this statement: ATM [ Now, isn't there an issue as to whether to use UDDI or ebXML? Manes: I don't think there's an issue at all. There's a spec out there called ebXML Registry, but nobody's using it. ] can see here: http://farrukhnajmi.blogspot.com/2007/02/here-is-piece-of-fud-regarding-ebxml_07.html Farrukh has been the spec lead on the ebXML registry/repository *standard* and is quite passionate about it. I agree that ebXML RR doesn't have the hype and support behind it that UDDI does, but it is more feature-rich than UDDI and certainly shouldn't be dismissed in the way that the above comment is presented in the article. Indeed, the article goes on to name Infravio as a UDDI registry. Infravio (AFAIK) is an ebXML RR based registry which provides a UDDI interface in addition to its ebXML RR one. Jason
