[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] UDDI as the registry for ebXML components: Typo?
I doubt that very many people will abandon .NET, WebLogic, WebSphere, etc. in favor of an ebMS solution. I know that BEA provides some ebXML support as an add-on product to WebLogic, but what news from IBM and Microsoft? Does anyone expect that these vendors plan to provide full support for an ebXML infrastructure? Based on current product offerings, I think it's fair to say that ebXML and Web services require different infrastructures. So I take it that you are requesting that the TN provide a little more background information on what is meant by ebXML and Web services infrastructure? That seems eminently reasonable. Anne ----- Original Message ----- From: "David RR Webber - XML ebusiness" <Gnosis_@compuserve.com> To: "Anne Thomas Manes" <firstname.lastname@example.org> Cc: "Chiusano Joseph" <email@example.com>; <firstname.lastname@example.org> Sent: Wednesday, July 02, 2003 11:58 AM Subject: Re: [regrep] UDDI as the registry for ebXML components: Typo? > Anne, > > Yes - but not to infer anything beyond that. For instance its entirely > possible to buy an ebMS solution from a vendor who has already > incorporated WSDL/ simple SOAP support - so the one product > can provide a combined delivery system. > > So now how does that sit with the statement that there is "significant > overhead", clearly it does not. > > It would be acceptable to point out that ebXML requires support > for ebMS and that more details on that are available at their site. > > DW. > ========================================================= > Message text written by "Anne Thomas Manes" > >You can register both SOAP/WSDL > services and ebXML services in a UDDI registry. Of course you can say the > same for an ebXML registry. But this is a UDDI TN, so it makes sense for > this TN to explain how to use UDDI to support both environments. > < >