DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7904>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7904 Tag Pool Manager - ClassCastException ------- Additional Comments From [EMAIL PROTECTED] 2002-04-11 01:13 ------- I got the clue !! It's not the TagPoolManager's fault, it's my fault... sorry... When tomcat is running and you compile some java class which is already loaded, then tomcat tries to reload such classes and that exception happens... - console says, AutoDeploy:reload xxxx the simple solution is to block all the reloadable options....as follows this may be plausible in production environment..... in server.xml, you can stop reloading context. <ReloadInterceptor fullReload="false"/> in app-xxx.xml, you can stop reloading servlet(?) <Context path="/xxx" docBase="webapps/xxx" debug="0" reloadable="false"> As i can see from jarkata web site, above two options has nothing to do with common java class, and they affect the reload of context and servlets(JSPs) .... but i don't know why the reload of common java class is affected... or is there any other options to stop reloading common java class ? or did i miss something ? thanks in advance... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
