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=33650>. 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=33650 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-19 18:04 ------- > You still need to "play nice" with regular Jasper mode, when compilation > occurs on access. I would complain if there are memory leaks, and/or abusive > memory usage ;) I think the cache needs to be enabled only in command line mode (batch compile). Otherwise it does not make much sense and it complicate things when you are development mode. > I would assume it would encourage many people to not bother with > precompilation It is totally different. Pre-compiling your jsp is mostly a way to check that there is no syntax or configuration problems with your taglibs or jsp. You don't care much with a petstore webapp with 10 jsps that you can check manually at deployment time, but with hundred of thems, it is not something you can afford. Assuming you have some QA dept or some automated robot to go through all your webpages, that's also useless to deliver something that does not even compile. So it's mostly a development thing and must be part of your process, and it should be part of the daily build as well of course. So if we can cut down this check from 12 to 1min, believe me I think some people would love it. -- 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]
