On Sun, 11 Nov 2001, Craig R. McClanahan wrote:
> ...
> There is no way in Java to persist a non-Serializable object like a
> database statement. In fact, you cannot even use such a thing if you're
> using a connection pool (completely separate from session persistance
> issues) unless the connection pool itself implements support for this.
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. these objects don't have to be persistent, but when
Tomcat is shut down it automatically tries to serialize the contents of
user sessions. when this happens i get warnings about the non-serializable
objects. i'd like to make these warnings go away. should i just put these
objects inside another class designed to store query state and implement
the Serializable interface (no serialization, just close handles) in this
class? are there any additional issues to take into consideration when
storing Statement and ResultSet objects inside sessions?
--
aspa
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
