Resultsets are not suitable constructs to be sending to a JSP. Not only do you hold DB resources open when you hang onto a result set for so long, the non-bean structure of the set is not suited for accessing through the EL.
Best practices dictate that, as soon as feasible, you copy the data from result sets into more suitable containers (array, lists, maps, and beans, as Arvind indicated) and pass those to the higher layers.
A fairly good
test of appropriate Separation of Concerns is to make sure that nothing in package java.sql (or javax.sql) is exposed outside of the data layer.
[ June 24, 2008: Message edited by: Bear Bibeault ]