Thanks. With session based bean passing, do you just remove the object from
the session when you're done using it to allow the garbage collector to
remove it from the heap when you're done? For instance, I'm working on a
form validation bean that I want to hand off to a JSP but I want it to
disaapear as soon as the page is displayed. I can imagine numerous sessions
filling up with these validation beans and causing the JDK to use a lot
resources. Also does using a session based bean imply thread safety?
> The setAttribute() call on both HttpServletRequest and ServletContext were
> added in the 2.1 servlet API, so they just are not going to be there
> with Apache JServ 1.0. However, you can still use session-scoped bean
passing,
> because the required calls (HttpSession.putValue and HttpSession.getValue) are
> present. I have used this quite successfully with GNUJSP.
>
> This week at JavaOne, Sun announced that they are licensing the reference
> implementations of JSDK and JSP to the Apache Project (that's us :-), for
> distribution under typical Apache licensing. In other words, they just open
> sourced two very key components of the Java2 Enterprise Edition architecture.
Very cool!!!
> This whole effort is just starting to get under way.
> For more information, or to contribute your time and talents, you will want to
> keep checking up on the new project web site:
>
> http://jakarta.apache.org
thanks, I'll check it out and see if I can do anything.
Mike
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
