I'm sure this issue has come up before, but I can't seem to find the right combination of search phrases to find solutions.
I know the proper way to deal with database access in MVC is to decouple that access from the presentation - usually by populating view beans with the results of database queries. Some folks even make reference to ResultSetUtils - which maps ResultSet data to collections of beans. But what if the amount of data returned is large? I can't really give some size off the top of my head, but say you returned a thousand rows to something the user would save in Excel or something? Or for whatever reason, the client didn't have a problem viewing a large amount of rows? I don't like the idea of copying all that data into objects in memory to later populate the page, but I also don't like the coupling of the cycling through the ResultSet to the view page itself. Is there some sort of an elegant compromise? Or have folks who have dealt with this just decided to live with the problem of cycling through a resultset in a JSP page, then remembering to close everything in the page? Thanks, Will Stranathan _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
