Well, it looks to me that short of overriding ActionServlet.process(), there
is no way one can clean-up resources after the page has been rendered...
----- Original Message -----
From: "Jeff Trent" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 10:54 PM
Subject: Re: Managing resource life cycle during request
> That's sounds okay for simple forms, but I'd rather not serialize objects
> from a multi-row recordset to a collection every time. Too much overhead!
> Let me put the question another way, in Struts, what method on the form or
> action class gets called following the rendering of the input page? I'll
> check source code now for this answer...
>
> - jeff
>
> ----- Original Message -----
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, June 04, 2001 9:25 PM
> Subject: Re: Managing resource life cycle during request
>
>
> > The types of objects I use for presentation should be disposed and
> > garbage collected. Here we would be talking about standard collections
> > of mainly Strings and maybe a few primitive types. Anything kinky would
> > be handled in the action. The view gets everything handed to it on a
> > silver platter.
> >
> > Jeff Trent wrote:
> > >
> > > Ted,
> > >
> > > Just because the objects are held in the bean doesn't necessary mean
> they
> > > will automatically be cleaned-up. Am I missing something here? I
also
> > > agree, I don't want to be writing queries within the JSP.
> > >
> > > Thanks,
> > > - jeff
> >
>
>
