Hi Mark, We didn't think of supporting docliteral.But since you mentioned it we might be able to support docliteral.
Damitha is working on the attachment support on client side. I don't know the status of it. Regards, Rangika ----- Original Message ----- From: "Mark Whitlock" <[EMAIL PROTECTED]> To: <axis-c-dev@ws.apache.org> Sent: Monday, April 25, 2005 9:03 PM Subject: Fw: Attachments > > > > > Hi Rangika, > Thanks for your quick response. Users will benefit from the attachment > support that you're putting in :-) > > I noticed that the soap message is rpc-encoded. Were you intending to > support doc-literal as well? > Also are you going to add in attachment support into the client as well as > the server? > > Thank you for your help, > Mark > Mark Whitlock > IBM > > ----- Forwarded by Mark Whitlock/UK/IBM on 25/04/2005 15:56 ----- > > "Rangika Mendis" > <[EMAIL PROTECTED] > ce.lk> To > "Apache AXIS C Developers List" > 25/04/2005 15:12 <axis-c-dev@ws.apache.org> > cc > > Please respond to Subject > "Apache AXIS C Re: Attachments > Developers List" > > > > > > > > > > Hi Mark, > > We are working on server side attachment support.There's a minor problem > but > other than that it's working fine. The code is committed to the cvs but > currently the code is commented. > > The web service sample is in > <Checkout>\samples\server\mime\ > > The client (Linux ) is in > <checkout>\tests\utils\simple-server-client\ > > The problem is the attachment id is displayed as an ASCII value in the > following text > <EchoAttachmentReturn xsi:type="xsd:string">?</EchoAttachmentReturn> (In > the response) > > The TCP Mon context are as follows.(Response) > > HTTP/1.1 200 OK > > Date: Mon, 25 Apr 2005 13:33:17 GMT > > Server: Apache/2.0.48 (Win32) > > Content-Length: 831 > > Connection: close > > Content-Type: text/xml > > > > > ------=MIME BOUNDARY > Content-Type: text/xml; charset=UTF-8 > > Content-Transfer-Encoding:8-bit > > Content-Id: <1505912FEDEB53D396BC22103DA3A51A> > > <?xml version='1.0' encoding='utf-8' ?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <SOAP-ENV:Body> > <ns1:EchoAttachmentResponse xmlns:ns1="urn:EchoAttachmentsService"> > <EchoAttachmentReturn xsi:type="xsd:string">?</EchoAttachmentReturn> > </ns1:EchoAttachmentResponse> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > > > ------=MIME BOUNDARY > > Content-Type:text/xml > Content-Transfer-Encoding:base64 > Content-Id: <000001233> > > SGVsbG8= > > ------=MIME BOUNDARY > > Content-Type:text/xml > Content-Transfer-Encoding:base64 > Content-Id: <000001234> > > R29vZA== > > ------=MIME BOUNDARY > > We're working on this currently. > > Regds > Rangika > > ----- Original Message ----- > From: "Mark Whitlock" <[EMAIL PROTECTED]> > To: <axis-c-dev@ws.apache.org> > Sent: Monday, April 25, 2005 7:26 PM > Subject: Attachments > > > > > > > > > > > > Hi, > > > > I was looking at the attachment support. Does anyone know... > > > > - whether attachments are currently being worked on and whether this > > support will be completed in 1.6? > > - whether Axis C++ will support attachments defined in the wsdl and > > referenced from the soap body? Or will these attachments be unreferenced? > > - will wsdl2ws be updated to support attachments? > > > > Thanks, > > Mark > > Mark Whitlock > > IBM > > > > > > > > > > >
