Thanks. Stef ----- Original Message ----- From: "Shawn Bayern" <[EMAIL PROTECTED]> To: "Tag Libraries Users List" <[EMAIL PROTECTED]> Sent: Monday, November 04, 2002 11:49 AM Subject: Re: JSTL Result Object and caching
> On Sun, 3 Nov 2002, Stefan wrote: > > > I am looking for information how the JSTL ResultObject deals with > > caching of resultsets derived from a Javabean method that returned a > > JDBC's rowset. When is the resultObject removed from memory, and/or > > how (if it is cached), can it be controlled? > > There are really questions for the JVM, not for application developers. > The object is eligible for removal once no references point to it; its > space can be recovered as soon as a page that created it in page scope > goes out of scope, for instance (or when a session expires, if it's stored > in session scope -- and so forth). > > > In a situation where I have a resultset that is displayed in a jsp > > using the JSTL <c:forEach> tag how can I set it up so that the > > resultsObject persist for say 1 minute so that when the page is loaded > > we don't have to go back to the database every time? > > This is a broader question; it's not the responsibility of the Result > object to "cache" results in this fashion. (It simply stores and "caches" > results with a lifecycle associated with that of the object.) > > You can use the Jakarta Taglibs "Cache Taglib" -- or other projects' > alternatives -- if you want open-ended, time-based caching. > > -- > Shawn Bayern > "JSTL in Action" http://www.jstlbook.com > > > -- > To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
