You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by David Wall <dw...@Yozons.com> on 2001/04/26 19:01:25 UTC
Plain old XML POSTed via HTTP(S)
I'm still in the early stages of testing out SOAP, but my scouring of
various lists and such seems to show that SOAP seems to be working about as
well as CORBA at interoperability. Of course, SOAP is much newer than
CORBA, but is it fair to say that the state of interoperability across
toolkits/languages/OSes is poor?
There are a lot of posts about problems getting MSFT (beta1 and beta2
causing additional compatibility problems) and Apache (seen problems with
changes from 2.0 to 2.1) to interoperate, and surely working with MSFT has
to be a goal, even if it means supporting "standards broken" formats, since
MSFT and their .NET world will likely be a large player in any SOAP service
(either as the client or the service).
Does anybody know if there's a good source of specific information about
what to do to make MSFT and Apache interoperate (in my case, I'm interested
in MSFT being the client, but I know others have interest where Apache is
the client)?
Are there any nasty issues just having a DOM create and XML string, and then
POSTing that via HTTP(S)? Would that likely be any more interoperable, or
will I just find that the XML string created by the different DOMs (MSFTs
verses Xerces) will have its own set of interoperability problems? I
suspect it wouldn't be too hard to "upgrade to SOAP" later if this approach
works.
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Plain old XML POSTed via HTTP(S)
Posted by Silvio Fiorito <si...@ntr.net>.
I think most of the problems seem to be with ApacheSOAP interop with .NET
Web Services (separate from MSSOAP 2.0). I've been using ApacheSOAP 2.1
clients with MSSOAP 2.0 servers for over a month now without a problem. I
haven't tried an MSSOAP client against an ApacheSOAP server yet, so I don't
know if there are any problems with that. Same thing with .NET: haven't used
it so I don't know what problems there are. I think the biggest problem is
with documentation on both sides. Also, IdooXOAP worked right out of the box
for me when I first tried it a month ago, but there were some speed issues.
I haven't gotten around to check it out again. MSSOAP as of today is now a
supported product (no longer beta) so maybe they'll focus more on interop
now that it's feature complete and out of beta.
Silvio
-----Original Message-----
From: David Wall [mailto:dwall@Yozons.com]
Sent: Thursday, April 26, 2001 1:01 PM
To: soap-user@xml.apache.org
Subject: Plain old XML POSTed via HTTP(S)
I'm still in the early stages of testing out SOAP, but my scouring of
various lists and such seems to show that SOAP seems to be working about as
well as CORBA at interoperability. Of course, SOAP is much newer than
CORBA, but is it fair to say that the state of interoperability across
toolkits/languages/OSes is poor?
There are a lot of posts about problems getting MSFT (beta1 and beta2
causing additional compatibility problems) and Apache (seen problems with
changes from 2.0 to 2.1) to interoperate, and surely working with MSFT has
to be a goal, even if it means supporting "standards broken" formats, since
MSFT and their .NET world will likely be a large player in any SOAP service
(either as the client or the service).
Does anybody know if there's a good source of specific information about
what to do to make MSFT and Apache interoperate (in my case, I'm interested
in MSFT being the client, but I know others have interest where Apache is
the client)?
Are there any nasty issues just having a DOM create and XML string, and then
POSTing that via HTTP(S)? Would that likely be any more interoperable, or
will I just find that the XML string created by the different DOMs (MSFTs
verses Xerces) will have its own set of interoperability problems? I
suspect it wouldn't be too hard to "upgrade to SOAP" later if this approach
works.
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Plain old XML POSTed via HTTP(S)
Posted by Silvio Fiorito <si...@ntr.net>.
I think most of the problems seem to be with ApacheSOAP interop with .NET
Web Services (separate from MSSOAP 2.0). I've been using ApacheSOAP 2.1
clients with MSSOAP 2.0 servers for over a month now without a problem. I
haven't tried an MSSOAP client against an ApacheSOAP server yet, so I don't
know if there are any problems with that. Same thing with .NET: haven't used
it so I don't know what problems there are. I think the biggest problem is
with documentation on both sides. Also, IdooXOAP worked right out of the box
for me when I first tried it a month ago, but there were some speed issues.
I haven't gotten around to check it out again. MSSOAP as of today is now a
supported product (no longer beta) so maybe they'll focus more on interop
now that it's feature complete and out of beta.
Silvio
-----Original Message-----
From: David Wall [mailto:dwall@Yozons.com]
Sent: Thursday, April 26, 2001 1:01 PM
To: soap-user@xml.apache.org
Subject: Plain old XML POSTed via HTTP(S)
I'm still in the early stages of testing out SOAP, but my scouring of
various lists and such seems to show that SOAP seems to be working about as
well as CORBA at interoperability. Of course, SOAP is much newer than
CORBA, but is it fair to say that the state of interoperability across
toolkits/languages/OSes is poor?
There are a lot of posts about problems getting MSFT (beta1 and beta2
causing additional compatibility problems) and Apache (seen problems with
changes from 2.0 to 2.1) to interoperate, and surely working with MSFT has
to be a goal, even if it means supporting "standards broken" formats, since
MSFT and their .NET world will likely be a large player in any SOAP service
(either as the client or the service).
Does anybody know if there's a good source of specific information about
what to do to make MSFT and Apache interoperate (in my case, I'm interested
in MSFT being the client, but I know others have interest where Apache is
the client)?
Are there any nasty issues just having a DOM create and XML string, and then
POSTing that via HTTP(S)? Would that likely be any more interoperable, or
will I just find that the XML string created by the different DOMs (MSFTs
verses Xerces) will have its own set of interoperability problems? I
suspect it wouldn't be too hard to "upgrade to SOAP" later if this approach
works.
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org