Can you elaborate on your resource cleanup requirements?
My view on designing a responsible object is that I must make sure it
eventually releases any, non-memory, finite resources it uses. This design
strategy, coupled with garbage collection ensures my system doesn't run out
of those resources (eg. file handles, sockets, etc.).
Given that ActionForms and JSPs should play the "view" role in Struts, I
would question a design that has them acquiring non-memory resources. But,
alas, I don't know your system or situation..
Regards,
Levi Cook
-----Original Message-----
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 10:31 PM
To: [EMAIL PROTECTED]
Subject: Re: Managing resource life cycle during request
I doubt that overriding ActionServlet.process() would work. The
controller sends back the response, and it's done. It's then up to HTTP
to deliver the view, usually a JSP.
Any clean-up routine would have to be the responsibility of the view,
which puts you into the scriplet zone.
Jeff Trent wrote:
>
> 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...
