You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Wouter Cloetens <wo...@mind.be> on 2001/05/01 02:36:18 UTC

Re: PDF

Very interesting, Anver. Always interested in improvements. Care to send
me your changes? I'll try to find the time to verify and commit them.

bfn, Wouter

On Mon, Apr 30, 2001 at 04:54:36PM -0400, Anver Sotnikov wrote:
> > 1. SOAP does not pass filename with attachment so you have to find a way 
> > to pass filename (it can be just an additional parameter)
> 
> You can specify it if you use a MimeBodyPart, I think.
> 
> I used DataHandler with Name in it - SOAP just lost it :o(
> I had to change Apache SOAP to fix it.
> 
> > 2. SOAP uses JavaMail to parse Mime Messages and JavaMail reads each 
> > MimePart in Memory :o( so if you send REALLY big file - you'll get 
> > OutOfMemory exception.
> > 
> > PS: Try to avoid using InputStream in SOAP method - otherwise Apache 
> Soap 
> > read it in byte array :o( use DataSource instead.
> 
> JavaMail will do the same thing with a DataSource. There is no way around 
> it
> - no matter how you read or write the data, it will be copied in memory,
> in both directions of the transmission.
> 
> Not exactly - I fixed SOAP implementation and now if we send file to 
> server it will be stored in memory only on server side... 
> If you use InputStream then SOAP will create ByteArrayDataSource and save 
> it in memory on client-side.
> In case of DataSource JavaMail just get InputStream from DS and send it to 
> server in chunks.
> But on server side during "parse" it loads each BodyPart in memory :o(

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