I've noticed that re-saving the JSP page will cause the new Bean to be used,
also.
tom
----- Original Message -----
From: "Randy Nielsen" <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Monday, October 23, 2000 8:44 AM
Subject: RE: Making changes to a bean or servlet
> By default, automatic reloading is only for servlets and JSP pages. You'll
> have to restart the JRun server to get the newest versions of beans and
> other non-servlet classes.
>
> For more information on reloadable and non-reloadable class libraries, refer
> to pages 54 and 55 of the Developing Applications with JRun manual.
>
> HTH
> Randy Nielsen
> Allaire Corp.
>
> -----Original Message-----
> From: Ralph Fiol [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, October 21, 2000 10:03 PM
> To: JRun-Talk
> Subject: Making changes to a bean or servlet
>
>
> When I create a bean, compile it, then call it from within a JSP page, all
> works fine. However, if I change the class, re-compile it, and run my JSP
> page again, it appears to be using the previously compiled bean. In other
> words, JRun does not seem to notice the newly compiled version. Same
> applies to Servlets. What's the trick?
>
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
