Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 9779 invoked from network); 5 Nov 2003 13:10:43 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Nov 2003 13:10:43 -0000 Received: (qmail 42635 invoked by uid 500); 5 Nov 2003 13:09:47 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 42594 invoked by uid 500); 5 Nov 2003 13:09:46 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Delivered-To: moderator for axis-dev@ws.apache.org Received: (qmail 68993 invoked from network); 5 Nov 2003 12:16:29 -0000 X-pair-Authenticated: 220.247.247.57 Message-ID: <010901c3a396$a3986000$0665a8c0@GTP200025> From: "Sanjaya Singharage" To: , "Nilay Hazra" References: Subject: Re: SOAP attachment: why I'm not getting faultstring? Date: Wed, 5 Nov 2003 18:16:25 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0106_01C3A3C8.ECDB0830" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0106_01C3A3C8.ECDB0830 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 1. I think that you are sending a post request to get the happyaxis.jsp = and axis is just obliging you with happy axis. Try deploying a web = service and then send the SOAP request as a POST to the correct uri for = that web service and I think you should get your soap fault 2. It shouldn't matter what language binding you have at either server = or client end. ----- Original Message -----=20 From: Nilay Hazra=20 To: axis-dev@ws.apache.org=20 Sent: Wednesday, November 05, 2003 12:48 PM Subject: SOAP attachment: why I'm not getting faultstring? Hi All, Forgive me if this seems to be a very basic question. I need to send a = file called myfile.txt as an attachment to my localhost server. My = localhost server consists of Jakarta Tomcat 4.1.27 with Apache Axis = configured. My client application is written in VC++ which actually = POSTs the following SOAP request to the URL = http://localhost:8080/axis/happyaxis.jsp [The URL mentioned is just for = testing, it is NOT capable of handling attachments] POST /axis/happyaxis.jsp HTTP/1.1 Host: LOCALHOST Content-Type: Multipart/Related; boundary=3DMIME_boundary; = type=3Dtext/xml; start=3D"" Content-Length: 188 --MIME_boundary Content-Type: text/xml; charset=3DUTF-8 Content-Transfer-Encoding: 8bit Content-ID: My questions are: 1. I'm getting a 200 OK message from server. I'm also expecting a SOAP = faultstring as a SOAP response from the server (since happyaxis.jsp is = not capable of handling attachments), instead I'm getting the the HTML = content of happyaxis.jsp. Why I'm not getting any SOAP faultstring? What = am I missing here? 2. If I need to handle attachments at the server, what else exactly I = need to do at the server side. Will it be a problem if I exchange SOAP = messages where my client code written in C++ and the server side = handling code written in JAVA. Once again, I apologize to anybody if he/she thinks that these are = very basic questions. Thank you in advance for any sort of help. Please mark a copy of your = mail to my id nhazra03@hotmail.com Nilay ------=_NextPart_000_0106_01C3A3C8.ECDB0830 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
1. I think that you are sending a post = request to=20 get the happyaxis.jsp and axis is just obliging you with happy = axis. Try=20 deploying a web service and then send the SOAP request as a POST to the = correct=20 uri for that web service and I think you should get your soap fault
2. It shouldn't matter what language binding you have at either = server or=20 client end.
----- Original Message -----
From:=20 Nilay=20 Hazra
Sent: Wednesday, November 05, = 2003 12:48=20 PM
Subject: SOAP attachment: why = I'm not=20 getting faultstring?

Hi All,
Forgive me if this seems to be a very = basic=20 question. I need to send a file called myfile.txt as an attachment to = my=20 localhost server. My localhost server consists of Jakarta Tomcat = 4.1.27 with=20 Apache Axis configured. My client application is written in VC++ which = actually POSTs the following SOAP request to the URL http://localhost:8080/a= xis/happyaxis.jsp [The=20 URL mentioned is just for testing, it is NOT capable of handling=20 attachments]
 
POST=20 /axis/happyaxis.jsp HTTP/1.1
Host:=20 LOCALHOST
Content-Type: Multipart/Related; = boundary=3DMIME_boundary;=20 type=3Dtext/xml; start=3D"<myfile@myurl.com>"
Content-Length: 188
--MIME_boundary
Content-Type: text/xml; charset=3DUTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <myfile@myurl.com>
<?xml=20 version=3D'1.0' ?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelop= e/">
<SOAP-ENV:Body>
<samplefile = href=3D"cid:myfile.txt"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
 
My=20 questions are:
1. I'm=20 getting a 200 OK message from server. I'm also expecting a SOAP=20 faultstring as a SOAP response from the server (since happyaxis.jsp is = not=20 capable of handling attachments), instead I'm getting the the HTML = content of=20 happyaxis.jsp. Why I'm not getting any SOAP faultstring? What am I = missing=20 here?
 
2. If I=20 need to handle attachments at the server, what else exactly I need to = do at=20 the server side. Will it be a problem if I exchange SOAP messages = where my=20 client code written in C++ and the server side handling code written = in=20 JAVA.
 
Once=20 again, I apologize to anybody if he/she thinks that these are very = basic=20 questions.
 
Thank=20 you in advance for any sort of help. Please mark a copy of your mail = to my id=20 nhazra03@hotmail.com
 
Nilay
------=_NextPart_000_0106_01C3A3C8.ECDB0830--