It sounds more like a design issue than a limitation in axis.Is this a limitation of axis? If so, then I guess chopping to several small chucks will be my last resort. =(
Have you tried to use -mx1000M as a switch for java? That way you have a larger memory?
Also, you may find it better to turn the vector into an array of strings, and then send the array back to the client, besides being more portable between MS and java.
Also, verify that you trimmed each string before storing it.
You may want to run a unit test, with a profiler and see where your memory is being absorbed. You may be leaking memory while doing the task, and so wasting memory.
-- "We do not lose our identity in our relations with others; in part, at least, we achieve our identity by those relations." Tony Blair, 1993
