Any precompiled classes (unlike JSPs) are loaded into server memory upon first
request. They are not dumped until you restart the server. So yes, you will have
to restart the server everytime you make a change to the bean. I am doing that
myself right now in fact. That is one thing I love about JSP, changes to a jsp
page DO NOT require you to restart the server.
Brian N. Burridge
Lead Internet Analyst
Cox Target Media
Michael Rumpf wrote:
> Hi !
>
> I am writing JSPs with a bean included into the page. When I change the bean
> the changes are not reflected to the implementation. This means, when I
> reload the page, e.g. a newly added method, being called from the JSP causes
> an exception to be raised: method yyy not found in xxx !
> Sometimes when I restart Apache the new version of the bean is used and the
> correct version of the bean seems to be instantiated.
> Because I am fairly new to the JSP community this is maybe a normal
> behaviour. I hope not, because I do not want the Apache to be restarted each
> time I change the bean :=(, but if so please point me to a good tutorial on
> session management in JSP.
>
> Configuration:
> --------------
> Sun Solaris 2.6
> Apache 1.3.6
> JServ 1.0b4
> GNU JSP 0.9.9 (0.91 spec)
>
> Michael Rumpf
> AASaM
> Luxembourg
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
