> We are following model 2 architecture to develop an application on
> Tomcat3.1 server. But we encounter a problem whenever we recompile the
> controller servlet code, we have to restart Tomcat server; otherwise,
> JSP page will get "java.lang.ClassCastException" which relates to the
> code we use to cast a java bean after retrieved it from session object
> inside JSP code. (By the way, we have edited the "conf/server.xml" file
>
> so that the application codes are reloadable.)
my belief is that the reloadable attribute just ensures reloading of a
servlet if it's changed (it happens when the user tries to access that
servlet). It does not reload any supporting classes if they have changed. So
i guess, u will HAVE to restart the servlet engine everytime u change the
supporting classes.
parag.
>
> We are anxious to know if anyone encounter the similar problem and how
> to solve it.
>
> Thanks,
>
> --
> Laiwu Luo
>
>
===========================================================================
> 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
===========================================================================
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
