On Wed, 15 Aug 2001, Dan - Blue Lotus Software wrote:
> Just a quick question. Is the preference to use ebXML for web services
> instead of SOAP?
No, ebXML uses SOAP as its transport.
> The reason I ask is that I saw a technical demonstration of ebXML and the
> XML-One conference in London about 5 months ago, and it looked seriously
> undercooked. As in, it looked like the demo was held together by bubblegum
> and duct tape. I had since written it off as the non-MS solution to compete
> with SOAP
It's more like a non-MS solution to the MS BizTalk servers.
It is really a platform for building b2b applications that support a whole
lot of features, including the transport (SOAP), messaging (sort of JMS
like), registry (UDDI competes here), Business Service Interfaces (I guess
competes with WSDL) also something called Collaboration Protocol Profiles
and Collaboration Protocol Agreements that allows the parties to negotiate
how the messages are being sent back and forth between the trading
partners. They also go to some length describing how the business
processes should be exposed in the ebXML registry.
It is really a big big spec :) It goes beyond what the UDDI/WSDL define
today.
There was overlap in the transport layer before but the ebxml spec writers
made the transition to SOAP, I think after SOAP 1.1 came out and
addressed some of the issues they had with it. There's still overlap in
the registry, UDDI and ebXML registries do have some differences in (I
can't remember how fundamental on the top of my head), there's been talk
about merging that too but don't know if any progress is made there.
-- Juha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
