You have to respect the fact that most vendors are really not at liberty to discuss client installations with the general public, and if they were would likely not for sound business/competitive reasons. We can only point to public sector stuff, and hope that individual users may be monitoring this list and wish to provide you with examples. -Matt On 21-Jul-04, at 9:10 AM, Bryan Rasmussen wrote: > I know that ebMS needs no other ebXML components, however in making > statements like that for other people to read it is often highly > beneficial > to point to cases in which ebMS has been used without using other ebXML > components, given that I'm not gonna be able to tell my boss or similar > level people, read the specification, they want to see something that > makes > them feel secure. This is why I'm asking onlist for all examples > people have > where ebMS has been implemented/used seperate from ebXML > implementation/usage. > > -----Oprindelig meddelelse----- > Fra: Matthew MacKenzie [mailto:mattm@adobe.com] > Sendt: 21. juli 2004 14:05 > Til: Bryan Rasmussen > Cc: ebxml-dev@lists.ebxml.org > Emne: Re: SV: ebms seperation from ebxml > > > As I said, ebMS needs no other ebXML components, its more or less > spelled out in the specification. Doc lit web services can be deployed > as ebMS services very easily. > > Also, re: UDDI -- ebxml does have its own Registry. Companies such as > Adobe (my employer) have implementations. > > -Mattt > > On 21-Jul-04, at 8:40 AM, Bryan Rasmussen wrote: > >> well actually that's what I meant, do you have any examples of these >> ebMS >> implementations without the CPP/A, with the CPP/A but without other >> ebXML >> framework involvement. The thing I would really like to figure out is, >> with >> all the stuff we have in house, how close are we to ebXML, as in what >> would >> we have to do to get there, and can we graduate that process, take our >> doc-literal webservices for example, reformulate as ebMS messages and >> so >> forth. >> >> I'm looking at it like this, we have a registry (UDDI), we have some >> sort of >> repository which pretty much just returns objects in the filesystem >> combined >> with metadata, we have various services and business processes, we >> have a >> procurement system running somewhere passing UBL documents, the more I >> look >> at it the more I start thinking that ebXML is indicated. >> >> -----Oprindelig meddelelse----- >> Fra: Matthew MacKenzie [mailto:mattm@adobe.com] >> Sendt: 21. juli 2004 13:29 >> Til: Bryan Rasmussen >> Cc: ebxml-dev@lists.ebxml.org >> Emne: Re: ebms seperation from ebxml >> >> >> Bryan, >> >> I know this is not an example, but I would like to point out that ebMS >> can be used in any place where document-literal web services are in >> use. It really doesn't rely on any other parts of the ebMS stack -- >> even CPP/A can be and is omitted from many ebMS implementations. >> >> -Matt >> >> On 21-Jul-04, at 6:59 AM, Bryan Rasmussen wrote: >> >>> Does anyone have any examples of ebms usage seperate from the ebxml >>> architecture? >>> >>> The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> >>> The >>> list archives are at http://lists.ebxml.org/archives/ebxml-dev/ >>> To subscribe or unsubscribe from this list use the subscription >>> manager: >>> <http://www.oasis-open.org/mlmanage/> >>> >> >> The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> >> The >> list archives are at http://lists.ebxml.org/archives/ebxml-dev/ >> To subscribe or unsubscribe from this list use the subscription >> manager: >> <http://www.oasis-open.org/mlmanage/> >> > > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> > The > list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the subscription > manager: > <http://www.oasis-open.org/mlmanage/> > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/>
<<attachment: winmail.dat>>