amething. Bottom line for me: upgrade to Tomcat 5.X if
you are going to use attachements and have .NET clients.
--Brad
-Original Message-
From: David Keyes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 8:21 AM
To: [EMAIL PROTECTED]
Subject: RE: Attachment from Axis service causing
sp1 client:
"Client found response content type of
'application/dime;charset=ISO-8859-1', but expected 'text/xml'."
Arg!
-Original Message-
From: Abhinav Maheshwari [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 9:59 AM
To: [EMAIL PROTECTED]
x27;application/dime;charset=ISO-8859-1', but
expected 'text/xml'."
Arg!
-Original Message-
From: Abhinav Maheshwari [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 9:59 AM
To: [EMAIL PROTECTED]
Subject: RE: Attachment from Axis service causing .NET to Er
without manually changing the automatically generated proxy.
I will look into that also. Let me know if this helps.
Best regards,
Abhinav Maheshwari
-Original Message-
From: Jim Collins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 2:16 AM
To: [EMAIL PROTECTED]
Subject: Re: Attach
ROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 22, 2004 3:52 PM
Subject: RE: Attachment from Axis service causing .NET to Error
> Yes, I'm using WSE10SP1. Uploading an attachment works fine, downloading
> from Axis on tomcat 4.1.29 fails with the message indicated belo
--Brad
-Original Message-
From: Abhinav Maheshwari [mailto:[EMAIL PROTECTED]
Sent: Monday, March 22, 2004 4:06 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Attachment from Axis service causing .NET to Error
Hi Sergeant,
Do you have the Web Service Enhancements 1.0 with Servic
Hi Sergeant,
Do you have the Web Service Enhancements 1.0 with Service Pack 1 installed
on your Visual Studio ? This is necessary to handle attachments on the .NET
client. In my opinion, the problem is not due to charset but the content
type 'application/dime'.
In case, this does not resolve your
