|
I was not advocating for a completely stateless application, just that the "outside of the Java box" should preferrably be stateless. Additionally I was just thinking of the session scope in a webapp, not a complete EJB-solution (which is overly complex for most purposes).
Since JDBC 3.0 allows for moving both back and forth in a resultset (this is from memory, so the names may be different) I would use plain SQL over JDBC and put the resultset in the session bean along with a counter stating the current row number so paging is possible. It should be trivially simple, but I'll need to do a quick and dirty test to see if it actually is so :)As far as I know, scrollable resultsets cannot be placed in stateless session beans.
Please, try it out. Let us know.I'll see what I can do :)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.