I know this most likely doesn't sound like the best idea. But I need to support paging of results sets. I was asked to allow a call to a session bean that ends up being a jdbc query only return 100 rows at a time. So my first thought was to return a session bean that implements an iterator pattern but is it legal to keep the connection open/resultSet between calls. In order to keep the result set valid the connection must be open. I know this will most likely lead to a connection leak, resource conflicts etc. But I might implement a timeout to invalidate the bean.
I looked at the CachedRowSet this seems like a good fit except it might suck up a lot of memory. Any other suggestions/ideas? Has anyone else had to do this? Thanks, jcl. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
