RE: Slighlty different content type error with newsoap-nightly.j ar

[Olivier Thomas <ol...@wanadoo.fr>]

Congratulations !
Do you think it should be easy to implement a SOAP slient with MS SOAP
Toolkit allowing file transfer ?

-----Original Message-----
From: Singleton, Owen [mailto:owen.singleton@csg.ch]
Sent: mercredi 17 janvier 2001 09:15
To: 'soap-user@xml.apache.org'; 'wcloeten@raleigh.ibm.com'
Subject: RE: Slighlty different content type error with
newsoap-nightly.j ar


Success!!

I've replaced the 1.2 mail.jar with the 1.1.3 version and it worked.  It
worked fine with a 1.2 version on the server and a 1.1.3 on the client too.

Funny that you only saw the problem intermittently.  It was a 100%
consistant failure on both Linux (JDK 1.1.8 & 1.3.0) & NT (JDK 1.2.2) over
here.

This was solved in the nick of time.  I'm giving a presentation tomorrow on
Soap to my management.  The ability to transfer files is a major plus for
us.  I think all the required functional points have been met.

Please let me know if there is anything more you'd like me to test for the
upcoming 2.1 release.

Thanks

Owen

ps here's the http traffic

Request
--------------------------------------
HTTP/1.0 200 OK Content-Type: text/xml; charset=utf-8 Content-Length: 508
Set-Cookie2: JSESSIONID=czb3bwrlu1;Version=1;Discard;Path="/soap"
Set-Cookie: JSESSIONID=czb3bwrlu1;Path=/soap Servlet-Engine: Tomcat Web
Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.3.0; Linux 2.2.14-5.0 i386;
java.vendor=Sun Microsystems Inc.)  <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:sendFileResponse xmlns:ns1="urn:mimetest"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xsi:type="xsd:string">Received attachment:
Content type: text/plain
Name:
Content class: java.lang.String
Content: bar!</return>
</ns1:sendFileResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Reply
---------------------------------------
POST /soap/servlet/rpcrouter HTTP/1.0 Host: localhost:8010 Content-Type:
multipart/related; boundary=8152936.979754245268.JavaMail.osinglet.luxdev;
type="text/xml"; start="2636682.979754245419.apache-soap.osinglet.luxdev"
Content-Length: 886 SOAPAction:
"  --8152936.979754245268.JavaMail.osinglet.luxdev Content-Type: text/xml;
charset=utf-8 Content-Transfer-Encoding: 8bit Content-ID:
<2636682.979754245419.apache-soap.osinglet.luxdev> Content-Length: 427
<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:sendFile xmlns:ns1="urn:mimetest"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<addedfile href ="cid:558937.979754245243.apache-soap.osinglet.luxdev"/>
</ns1:sendFile>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> --8152936.979754245268.JavaMail.osinglet.luxdev
Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-ID:
<558937.979754245243.apache-soap.osinglet.luxdev> Content-Length: 4
 bar! --8152936.979754245268.JavaMail.osinglet.luxdev--


-----Original Message-----
From: wcloeten@raleigh.ibm.com [mailto:wcloeten@raleigh.ibm.com]
Sent: mercredi 17 janvier 2001 17:36
To: soap-user@xml.apache.org
Subject: RE: Slighlty different content type error with new
soap-nightly.j ar


Ha. JavaMail 1.2 has been released in December, I didn't notice that.
I'll fix it so we support that version too. In the mean time, you could
try 1.1.3; it's still on the website.

Bug #4293605 reports that the generated boundary string was invalid, as
the MIME RFC does not allow the '@' character. That fix is probably the
cause of this.

I downloaded it and very intermittently, I do see the same problem
you're reporting. It normally works fine; it doesn't look like any of
my code gets confused by the differently formatted boundary string. The
new mail.jar does cause another problem too. I've fixed that already,
but I'll wait until I get to the bottom of this before I commit the
fix.

bfn,
Wouter

On Wed, 17 Jan 2001 16:20:14 +0100, Singleton, Owen wrote:

Content-Type: multipart/related; ; type="text/xml";
start="-1181061126.979744032730.apache-soap.osinglet.wlux2020274"
Content-Length: 922 SOAPAction: ""

>-----Original Message-----
>From: wcloeten@raleigh.ibm.com [mailto:wcloeten@raleigh.ibm.com]
>Sent: mardi 16 janvier 2001 23:55
>To: Owen Singleton; soap-user@xml.apache.org
>Subject: Re: Slighlty different content type error with new
>soap-nightly.jar
>
>
>AH! Gravity's pulling on my penny here.
>
>On Tue, 16 Jan 2001 16:23:53 +0100, Singleton, Owen wrote:
>[...]
>java.io.IOException: Message is empty!
>>at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:33
7)
>[...]
>
>Right, that's a bug. Faults do not get generated properly. Shinta
>reported it too. Dug and I just fixed it and are testing it before we
>commit. There should be a fixed version up later today.
>
>Something hit me, reading through your posts though:
>
>>--------------------------------------------------------------------------
-----
>>Request Message
>>--------------------------------------------------------------------------
----
>>
>>POST /soap/servlet/rpcrouter HTTP/1.0
>>Host: localhost:8010
>>Content-Type: multipart/related; ; type="text/xml";
start="3708984.979661619847.apache-soap.osinglet.luxdev"
>
>OK, notice the: boundary="...." missing, which is causing your
>problem...
>
>>Content-Length: 73622
>>SOAPAction: ""
>>
>>------=_Part_0_6631688.979661619693
>HA! There we go! Your boundary string has an "=" sign in it! That may
>be what's throwing off my parsing code and screwing up the Content-Type
>header.
>
>This is what a unique boundary value, generated by JavaMail, looks like
>on my system:
>"201553.979685070526.JavaMail.wcloeten@roadkill.greenock.uk.ibm.com".
>
>This comment is copied from the JavaMail source:
>// Unique string is <hashcode>.<currentTime>.JavaMail.<suffix>
>where <suffix> is the userid@hostname of the local system, and
><hashcode> is a hash code for some random new object. You can tell that
>I've followed JavaMail's example when I wrote code to generate random
>unique Content-ID strings.
>
>Needless to say, I am stupefied by the format your boundary string.
>Could you tell me precisely where you got your version of JavaMail? Do
>you have it as part of the J2EE or something?
>
>With a bit of luck, all I need to do is change some of my own parsing
>code, but I'd really like to know the full story...
>
>bfn, Wouter
>--
>http://www.workspot.net/~zombie/soap/
>My opinions are irrelevant. They will be assimilated by my employer.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
>For additional commands, email: soap-user-help@xml.apache.org
>
>This message is for the named person's use only.  It may contain
>confidential, proprietary or legally privileged information.  No
>confidentiality or privilege is waived or lost by any mistransmission.
>If you receive this message in error, please immediately delete it and all
>copies of it from your system, destroy any hard copies of it and notify the
>sender.  You must not, directly or indirectly, use, disclose, distribute,
>print, or copy any part of this message if you are not the intended
>recipient. CREDIT SUISSE GROUP and each of its subsidiaries each reserve
>the right to monitor all e-mail communications through its networks.  Any
>views expressed in this message are those of the individual sender, except
>where the message states otherwise and the sender is authorised to state
>them to be the views of any such entity.
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
>For additional commands, email: soap-user-help@xml.apache.org
>

--
http://www.workspot.net/~zombie/soap/
My opinions are irrelevant. They will be assimilated by my employer.


---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org

This message is for the named person's use only.  It may contain
confidential, proprietary or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender.  You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. CREDIT SUISSE GROUP and each of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.  Any
views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state
them to be the views of any such entity.




---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org