On May 15, 2008, at 11:30 PM, rafael.munoz wrote: > > Hi > > I was trying to precompile my JSPs before the deploy phase and, > thanks to > the help of people of this mail list, I got it. My problem now is > that Resin > is not taking account of the compiled JSPs and it's compiling again > the JSPs > in the first access. The smap, java and class file per JSPs are > inside my > war and they seems OK. It's just that Resin seems decide that > they're not > longer valid and have to compile them again. > > Anybody knows why? What is the algorithm that Resin uses to know > that have > to compile again the JSP? Is it base in the file timestamp or > anything? Is > it a Resin configuration issue?
It should be based on the digest of the JSP file, but it also depends on your tag libraries. So if there's a different in the tag jars between the compilation and the deployment, you'd see a recompilation. You can also set <jsp auto-compile='false'/> to force Resin to not recompile. (I'm not sure that's the best solution, but it's possible.) -- Scott > > > I'm a little lost so any help will be appreciate. > > thanks in advance, > rafa > -- > View this message in context: > http://www.nabble.com/Resin-compiling-again-precompiled-JSPs-tp17268449p17268449.html > Sent from the Resin mailing list archive at Nabble.com. > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
