This won't make any difference to the amount of data which has to be serialized. The process of serializing/deserializing is memory intensive.
Yves On Fri, 2005-02-25 at 13:14 +0100, Sebastien Mayemba Mbokoso wrote: > I think the best way is u try to create a class which can make > compression. So u're going > to use the class both in the client side and the server side. The > client side for the uncompression and the server for the compression. > For the compression i think that u have > two choices : hardware or software (Jax RPC Handler, Servlet filter). > Bill don't keep in mind > i didn't try that before. It's just an idea i am giving you. > > ----------- > Sebastien > > On Fri, 25 Feb 2005 11:12:06 +0900, Bill Keese > <[EMAIL PROTECTED]> wrote: > > Solving this problem for client and server are pretty similar. You > > probably need to bump up your client memory size to 128M instead of the > > default 64M (-Xmx128m option to "java"). And you should try the newest > > Xerces, etc. I am passing 4MB strings with no problem. > > > > Justin Echternach wrote: > > > > >I am getting an OutOfMemoryError when passing an xml string to a web > > >service > > >using axis. The xml string is 5 Mb long. > > > > > >I read many different threads with the same error, but didn't come across a > > >resolution. Is there a way to make this work with Axis without using SOAP > > >w/ attachments? > > > > > >I am in a bind and need to be able to pass large strings to this web > > >service. > > > > > >Thanks in advance. > > > > > >Justin > > > > > > > > > > > > > > > > > >
