AW: JSP variable problem

[Ralph Einfeldt]

That's the beautifull thing, the objects that are bound
to the request will be released from memory as soon as
the request is finished. (Technically not perfercly true
they are just marked as 'not needed anymore' and will be
removed witg the next run of the garbage collector().
When and under which circumstances this run happens 
depends on the jvm).

 -Ursprüngliche Nachricht-
 Von: Raphael Di Cicco [mailto:[EMAIL PROTECTED]]
 Gesendet: Mittwoch, 10. Juli 2002 09:56
 An: Tomcat Users List; David Mossakowski
 Betreff: Re: JSP variable problem
 
 But when am I supposed to remove the object inside the 
 request from memory ?
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

AW: JSP variable problem

[Ralph Einfeldt]

Why do you store the objects in the session, if
you want to detroy them whenever you leave the
the page ?

Why not use something like this
% Object mResource = ... %

This kind of object will just live as long as the 
request is processed. 

If you want to store objects that have to be accessed
by dynamically included pages you can define beans 
with request scope.

If your objects are no beans you can use 
pageContext.setAttribute(ResourceName,
 mResource,
 PageContext.REQUEST_SCOPE);

 -Ursprüngliche Nachricht-
 Von: Raphael Di Cicco [mailto:[EMAIL PROTECTED]]
 Gesendet: Dienstag, 9. Juli 2002 10:50
 An: Tomcat Users List
 Betreff: JSP variable problem
 
 The problem is that this is very heavy in memory, I want to 
 destroy every 
 myRessource once I quit the page. I tried to use jspDetroy 
 method but :
 I have no idea when exactly this is called
 I cannot use my index variable in it
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]