Shannon Moschetti wrote:
>
> After a little detective work I discovered that(I can only verifiy that this
> is the case for JRun) when you instantiate a session scoped bean, under the
> covers the JRun servlet code does a
> httpsession.putValue(beanName,beanValue). So for all of you who have wanted
> to know how to get rid of a bean when you don't need or want it anymore, you
> can simply: httpsession.removeValue(beanName). Why they don't seem to have
> a tag to do this is beyond me. I suspected this to be the case, but wasn't
> sure until now. I hope this helps some.
This is standard for all compliant containers; session scope beans are stored
as HttpSession attributes, application scope beans as ServletContext attributes,
request scope as HttpServletRequest attributes, and page scope as PageContext
attributes. See the JSP specification for details.
I agree a tag for this, and for invalidation of a session, would be good
additions to the spec.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
