This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm somewhat of a Web Services newbie. I am trying to modify an existing web service that FTPs a CSV file from a legacy system, reads through it, and writes some XML out to the web service. It is pretty top-down in that (for the most part) it reads a line of CSV, writes out a chunk of XML, rinse, repeat.
We are using Apache Axis 1.4 and what appears to happen is that Axis / Apache builds the whole String in memory before writing out the response.
Because the files we are sending are quite large, we occasionally run out of memory while processing them. As part of the rewrite of the service, I'm being asked to rewrite the service so that it takes up less memory.
In doing a bit of reading around I have come across the concept that for large files, the best practice is to use SAAJ / attachments.
I was wondering if anyone had any pointers to some good introductory lessons on that? I've read
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
Joined: Nov 19, 2008
Thanks for taking the time to reply.
Now, I may be misreading the links that you sent (such are the downsides of not totally understanding the basic framework), but both of those links seem to talk about how to READ attachments when consuming a web service.
I am trying to PROVIDE attachments as part of the service.