DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33453>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33453 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-08 05:29 ------- What are the side-effects of revalidating the entire tree ? Does it cause all class files to be loaded or can the revalidation occur without having any lasting overheads (like increased memory consumption and slower revalidation process due to parsing of more complex .class data). My method only seeks to delete stale work/ .java and .class files during web-app deployment. It does not seek to recreate and load them, that can be left to moment of first use (although it would natually lead on to facilitating an automatic recreation function). By opening the .java file and looking for a magic comment and closing the file again, there is no lasting overhead. Since we never loaded the class. Which is just great for a revalidation pass during deployment. I'm a believer there should be a configuration mode of TC which is watertight, such that no amount of abuse will make the things fail in a way that bites you. The work/ directory is a nice speedup but the implementation is more a hack than an optimization, since it clearly breaks down in situations you wouldn't expect. This bug/problem hits developers a lot more than production upgrades. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
