Thanks for the excellent response. It was very informative. I was close
(when I compared ebXML to SOAP, I meant to compare it to SOAP, WSDL, &
UDDI).
My opinion of it back 5 months ago was that it was not really even close to
usable yet. Have things changed radically since then? Was I mistaken?
I know IBM have a UDDI implementation in beta. Any chance we can convince
them to donate it to Apache, Jakarta, or JBoss (I figure it's more likely
they would open-source it to one of the first two, given their currently
relationship with Apache)?
What needs to be added to provide WSDL support? Maybe I'm missing
something, but it seems like it's merely a "description language" for
services--a file you might retrieve from a UDDI registry that describes a
SOAP service. In this case, what is needed to provide support for WSDL?
Anything?
Sorry to ask all these questions at once. I had written off ebXML for the
near future--if I need to take another look at it, I want to know!
Thanks, guys. The knowledge & expertise on these lists is remarkable, and I
learn new stuff daily.
-dan
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Juha-P Lindfors
Sent: Wednesday, August 15, 2001 11:33 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] URGENCY? WSDL/UDDI/ebXML
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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
