Pae,
Forgive me. I never meant to imply that SOAP/WSDL/UDDI is better than ebXML.
I simply meant to say that they are different. And that Sun focused their
efforts on ebXML and was very reluctant to contribute to SOAP/WSDL/UDDI.
We started this conversation by talking about WS-I and why Sun wasn'
- Original Message -
From: "Pae Choi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 23, 2002 00:32
Subject: Re: Document style web services
> And that's true ebXML has own stuff all that you mentined.
> Shouldn't those considered as positive artifacts. They have fi
- Original Message -
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 22, 2002 18:55
Subject: RE: UPNP
> I haven't heard anything about UPNP for about a year. The only device that
I
> ever heard of that was UPNP certified was the Intel AnyPoint
- Original Message -
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 22, 2002 18:44
Subject: RE: Document style web services
>
> - JAXM was launched in June 2000. Originally it was an
> API for ebXML. Only later (once ebXML had adopted SOAP
Steve Loughran wrote:
As an aside, does *anyone* use UDDI?
-steve
I'm personally really puzzled by the logic behind UDDI. As far as I can
see there's a huge gap between the reality of what can be done using
UDDI and the marketing concept behind it (which seems to be that you can
have your p
UDDI like most directory services is mostly useful for those that helped
design it.
The .NET Visual Studio use of UDDI is quite helpful when you are
developing consumer applications against published UDDI Web Services,
which I believe is the point. Obviously if you are building a Web
Service and
Hello everybody,
I've almost my last "problem" with Axis.
I'm currently using Jboss.NET but want to change to Axis. My
Deploydescriptor is changed for the Axis-needs and looks like:
cmr.ContentSession
cmr.ContentSession
