Re: WebServices and .NET

From:

Lew <lew@lewscanon.nospam>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 15 Jun 2007 19:26:32 -0400

Message-ID:

<7vadnUuzl-a1ve7bnZ2dnUVZ_hninZ2d@comcast.com>

DTLLLUmpireSchedules@gmail.com wrote:

On May 12, 3:56 pm, Arne Vajh??j <a...@vajhoej.dk> wrote:

MikeSchillingwrote:

"Arne Vajh??j" <a...@vajhoej.dk> wrote ...

MikeSchillingwrote:

"Arne Vajh??j" <a...@vajhoej.dk> wrote

For some servlet containers you will need to tell the .NET
developers to put:
ServicePointManager.Expect100Continue= false;
in their program to avoid confusing the servlet container.

Which containers have you found this to be necessary for?

Tomcat.

Odd. At my workplace, we combine .NET clients and services deployed in
Tomcat(4.0 and 5.5) with some frequency (e.g. in the nightly unit tests),
don't set that flag, and haven't seen any problems.

It may very likely only be certain combinations of versions.

If you google for it, then you find several stories where it
was necessary to make it work.

Obviously those without the problem never posted so.

And now we've run into it, and this information is invaluable. score
one for Usenet, and thanks, Arne.

At a project last year our team used Apache Web server as a front end to
Tomcat running Apache Axis to do Web services connecting to both J2EE clients
and .Net clients. All we had to do was make the WSDL specify
"document-literal" and follow certain Microsoftisms to assure interoperability.

Could it be that we were lucky that either Apache Web Server lacks the issue
or that that version did?

I'm with DTLLLUmpireSchedules - I'm really glad you showed us this tip.

--
Lew