You're correct on 4.0, my container and worker beans become available immediately after changes are made with the testing we've done so far.
The problem I've had is with certain custom tags I've created from scratch that are feed off beans... changes there don't always recompile on 4.0... but that may be my problem, not a bug... In 3.1, you have to restart your JRun server for everything but JSP changes, in most cases (unless you've pre-compiled your JSP's). TD ---------- Original Message ---------------------------------- From: [EMAIL PROTECTED] (JRun-Talk) Reply-To: <[EMAIL PROTECTED]> Date: Sat, 29 Jun 2002 05:53:00 -0400 >JRun-Talk-List Sat, 29 Jun 2002 Volume 1 : Number 31 > >In this issue: > > Jrun 3.1 Cache HELP!!! > RE: Jrun 3.1 Cache HELP!!! > > >---------------------------------------------------------------------- > >Date: Fri, 28 Jun 2002 12:54:57 -0400 >From: "Boogie Brown" <[EMAIL PROTECTED]> >Subject: Jrun 3.1 Cache HELP!!! >Message-ID: <[EMAIL PROTECTED]> > >To whom it may concern: > >I am referencing a bean in Jrun 3.1 as shown below: ><jsp:useBean id="NewContent" class="setUpNewContentBean" scope="page"> ></jsp:useBean> > >however whenever I recompile the bean I am unable to see the updated results >of my bean. > >Please help. . . > >Thanks in advance. >Michael > > > > >______________________________________________________________________ >Get the JRun Web Application Construction Kit - the only book written specifically >for JRun developers. >http://www.amazon.com/exec/obidos/ASIN/0789726009/houseoffusion > >------------------------------ > >Date: Fri, 28 Jun 2002 11:57:45 -0500 >From: "Haseltine, Celeste" <[EMAIL PROTECTED]> >Subject: RE: Jrun 3.1 Cache HELP!!! >Message-ID: <[EMAIL PROTECTED]> > >Michael, > >You have restart the JRUN 3.1 server in order for your Java class bean >revisions to become available to your application. Unlike changes to your >JSP's and servlets, where JRUN for the most part can "sense" that a JSP or >servlet has been changed and recompile/reload it on the fly, your Java beans >are loaded into server memory the first time they are called, and remain in >memory until you reboot JRUN3.1. > >By the way, it is my understanding that this is no longer the case in JRUN >4.0. > >Celeste > >-----Original Message----- >From: Boogie Brown [mailto:[EMAIL PROTECTED]] >Sent: Friday, June 28, 2002 11:55 AM >To: JRun-Talk >Subject: Jrun 3.1 Cache HELP!!! > > >To whom it may concern: > >I am referencing a bean in Jrun 3.1 as shown below: ><jsp:useBean id="NewContent" class="setUpNewContentBean" scope="page"> ></jsp:useBean> > >however whenever I recompile the bean I am unable to see the updated results > >of my bean. > >Please help. . . > >Thanks in advance. >Michael > > > > > >______________________________________________________________________ >Your ad could be here. Monies from ads go to support these lists and provide more >resources for the community. http://www.fusionauthority.com/ads.cfm > >------------------------------ > >End of JRun-Talk-List V1 #31 >**************************** >Archives: http://www.mail-archive.com/[email protected]/ >Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists > > Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
