Anyone know how Axis manages attachments? I know that WASP uses stream processing, so has no message size limit. I'm not sure about open source solutions, though.
Anne > -----Original Message----- > From: Mike Kopack [mailto:mkopack@;isx.com] > Sent: Monday, October 28, 2002 1:31 PM > To: [EMAIL PROTECTED] > Subject: Re: A question about SOAP with attachments! > > > I can attest from experience that there is definately a limit in > Apache SOAP > in this regard. I am working on a SOAP xml-rpc based client/server > application that needs to be able to send files between the client and the > server. Whenever I tried to send the file along as a DataHandler or > Inputstream, if the file was bigger than around 18 MB in size I > would get a > "Out of Memory Error" on the side trying to send the file. > > My only way to get around this problem was to write a simple > "browser" that > could request files from the server and another that would perform an HTTP > Post to a JSP running on the server so I could send. While this works, it > circumvents our desire to use SOAP for everything and is a bit of a hack. > > The only thing I could come up with is that when you send > structures like an > Inputstream, Apache SOAP stores everything in memory as it's > building up the > envelope prior to sending it. As a result, large items eat up the > Java heap > space and a memory error occures. > > Sorry, wish I had better news... If anyone knows of a way around this > problem other than what I've outlined, I'd love to hear it! > > --Mike > > ----- Original Message ----- > From: "WJCarpenter" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, October 28, 2002 1:22 PM > Subject: RE: A question about SOAP with attachments! > > > > > Theoretically, there's no limit. But depending on how the SOAP runtime > > > deals with the messages, there may be a limit imposed by your system's > > > memory: i.e., if the SOAP runtime tries to load the message > into memory > > > before processing. You'll need a stream-based processor to deal with > > > unlimited size. > > > > Hear, hear. In particular, if you are contemplating using Apache > > SOAP 2.x, you should probably start looking at other solutions. Even > > for messages, the Apache SOAP 2.x client code is quite promiscuous in > > the number of in-memory copies it makes of the entire response payload. > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:soap-user-unsubscribe@;xml.apache.org> > > For additional commands, e-mail: <mailto:soap-user-help@;xml.apache.org> > > > > > > > -- > To unsubscribe, e-mail: <mailto:soap-user-unsubscribe@;xml.apache.org> > For additional commands, e-mail: <mailto:soap-user-help@;xml.apache.org> > -- To unsubscribe, e-mail: <mailto:soap-user-unsubscribe@;xml.apache.org> For additional commands, e-mail: <mailto:soap-user-help@;xml.apache.org>
