Pier Fumagalli wrote: > > "Remy Maucherat" <[EMAIL PROTECTED]> wrote: > > > Thanks for the report Pier. I had been wondering for AGES why the CL would > > reload the webapp "randomly" after accessing a JSP, telling that a bean > > class had been modified. I couldn't find a reason why it was a bug (the > > logging I added to investigate this displayed different dates which didn't > > appear bogus), but I failed to undestand why it happened. > > Yeah, I wonder why noone actually noticed this before... Am I the only idiot > using TC4 in a secure production environment? (Meaning, chrooted JVM and > suid execution, with access only to the "work" directory)?
Last time I have tried this I noted that it did not work: TC tries to write in several places (at least conf and webapps). > > > Jasper 2 has some big advantages in production, like being able to disable > > reloading checks altogether, as well as various other optimizations, which > > makes the JSP overhead over a servlet almost zero. Obviously, the fix for > > bug 8290 is also a huge improvement if you're using a lot of tags. > > Lately, I have found some incompatibilities with JSTL (their examples WAR > > doesn't really like Jasper 2); the admin webapp (big Struts webapp which is > > painfully slow with Jasper 1 - and that's with one user on an Athlon XP > > 1700+ ;-) ) and Watchdog both run very well, though. > > Yeah, I'm not going to start using it for http://www.vnunet.com/ anyway for > another while anyway... We've got some beefy hardware behind that site, so > speed is not an issue, but if one page goes wild, my salary starts going > down. No thanks, I'll wait... > > Pier > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
