It is not a good idea at all to store the standard Connections and ResultSets in the session.
- This will eat up your connections to the database - The ResultSet is tied to a Connection, this connection may timeout at any given time. The database server can decide on any criteria it likes to close the underlying connection. (Typically an inactivity timeout) Possible solution: - Use a CachedResultSet; some ConnectionPools implement something like that, or have a look at http://developer.java.sun.com/developer/earlyAccess/crs/ (Requires login) > -----Ursprüngliche Nachricht----- > Von: Marko Asplund [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 12. November 2001 19:49 > An: Tomcat Users List > Betreff: Re: non-serializable objects in sessions <snip/ > what i'd like to do is store Statement and ResultSet objects in a user > session so, that the data fetched from the database can be > paginated more easily for the user. <snip/ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
