Josh,
 
I had that problem too, you might try putting the following line before the this.Invoke(...) method call in Reference.cs
 
this.RequestSoapContext.Path.MustUnderstand = false;
 
Jeff
-----Original Message-----
From: Josh Kropf [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 11, 2003 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: DIME & Axis (2)

Maurizio,
 
I am assuming since you are working with attachments in your .NET client you are using the WSE 1.0 for .NET. Have you had any issues when sending the soap request to Axis? I seem to be having difficulties getting Axis to accept the request sent from the C# client derived from the WSE 1.0 class Microsoft.Web.Services.WebServicesClientProtocol
 
Axis complains that it can't understand some part of the header.
-----Original Message-----
From: Maurizio Sciglio [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 10, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: Re: DIME & Axis (2)

I can't believe! It was a problem with TCPMonitor! For some weird reason the use of tunnelling cause stream interruption.
----- Original Message -----
Sent: Monday, February 10, 2003 6:38 PM
Subject: DIME & Axis (2)

Hi all again.
 
I've written a web service (with Axis) to receive files sent from a C# Client. To try the service I'm using some GIF images. Often the service call fails and the following message appears within the Tomcat window :
 
java.io.IOException : End of physical stream detected when xxx more bytes expected.
 
If I try to send text/plain everything work fine. Maybe with the images Axis find an End of file character? If so, is there a way to avoid this problem?
 
Thanx
  Maurizio Sciglio

Reply via email to