You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Eduardo Yanez <ey...@eversystems.com> on 2001/07/10 19:34:52 UTC
Bug in mime Apache SOAP samples
The SOAP 2.2 version has a bug in their mime samples. (Please use fixed font
to read this email)
I set my classpath to:
set CLASSPATH=E:\soap-2_2;
E:\soap-2_2\lib\xerces.jar;
E:\soap-2_2\lib\soap.jar;
E:\soap-2_2\lib\mail.jar;
E:\soap-2_2\lib\activation.jar;. <-- My classpath
Then I run the "soap-2_2/samples/mime/testit.cmd" batch file step by step:
set URL=http://localhost:8082/soap/servlet/rpcrouter <-- for the Tcp Tunnel
Monitor
(My servlet engine
is listening on port 8080)
set BASEDIR=E:\soap-2_2\samples\mime\ <-- My basedir value
java org.apache.soap.server.ServiceManagerClient %URL% deploy
DeploymentDescriptor.xml <-- success!
java org.apache.soap.server.ServiceManagerClient %URL% list <-- success!
Output:
Deployed Services:
urn:mimetest
java samples.mime.MimeTestClient %URL% sendFile foo.txt <-- success!
Output:
Received attachment:
Content type: text/plain
Name: null
Content class: java.lang.String
Content: bar!
java samples.mime.MimeTestClient %URL% loopFile fields.gif <-- Error!! :-(
Output:
Caught SOAPException (SOAP-ENV:Client):
Error parsing response:
javax.mail.MessagingException: Missing start boundary
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing
response: javax.mail.MessagingException:
Missing start boundary;
targetException=java.lang.IllegalArgumentException: Error parsing response:
javax.mail.MessagingException: Missing start boundary]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
va:324)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at samples.mime.MimeTestClient.main(MimeTestClient.java:159)
The Tcp Tunnel output is this:
***.- Request SOAP envelope:
POST /soap/servlet/rpcrouter HTTP/1.0
Host: localhost
Content-Type: multipart/related;
boundary="----=_Part_0_444082.994784837652"; type="text/xml";
start="7453641.994784837712.apache-soap.serverey"
Content-Length: 2115
SOAPAction: ""
------=_Part_0_444082.994784837652
Content-Type: text/xml; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-ID: <7453641.994784837712.apache-soap.serverey>
Content-Length: 469
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:loopFile xmlns:ns1="urn:mimetest"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<addedfile href ="cid:7901508.994784837642.apache-soap.serverey"/>
</ns1:loopFile>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
------=_Part_0_444082.994784837652
Content-Type: image/gif
Content-Transfer-Encoding: 8bit
Content-ID: <7901508.994784837642.apache-soap.serverey>
Content-Length: 1241
GIF89al3fT3fI3fy3To?v?,a|6AG ?z?c^ U#"E&A!<qYa.7a"'Mu^%-u
...
***.- Response SOAP envelope:
HTTP/1.0 200 OK
Server: EvApps/1.2.5
Set-Cookie: JSESSIONID=aaacY4X8h_v-eS;
Path=/
Content-Type: multipart/related
Content-Length: 2114
Date: Tue, 10 Jul 2001 17:07:17 GMT
------=_Part_11_3539584.994784837882
Content-Type: text/xml; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-ID: <4871666.994784837882.apache-soap.serverey>
Content-Length: 484
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:loopFileResponse xmlns:ns1="urn:mimetest"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return href ="cid:7971559.994784837882.apache-soap.serverey"/>
</ns1:loopFileResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
------=_Part_11_3539584.994784837882
Content-Type: image/gif
Content-Transfer-Encoding: 8bit
Content-ID: <7971559.994784837882.apache-soap.serverey>
GIF89alNf#NutXEXagR+[uf"R?O?OoiAo?a,
...
I can see that the response buffer does not have a start boundary
specification like the request buffer has
(start="7453641.994784837712.apache-soap.serverey") i think this is the
cause.
I wish to know where to find the components (all the *.jar files) to build
SOAP by my self and aid to the project in finding this bug. Is another way
in which i could help?. (appart from using soap of course).
Regards,
Eduardo Yanez.
How to help
Posted by Eduardo Yanez <ey...@eversystems.com>.
Hi SOAP developers!
If i?m also an XML-Java developer, how could i help to the project??
Regards,
E.Y.