AW: JSP pre-compile and Apache
Well there is one big advantage when using precompiled JSPs: You're sure that all JSPs are compilable, so you don't get any compile errors on your live site. That gives your application more stability. Bernhard -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. Juni 2005 08:07 An: Tomcat Users List Betreff: Re: JSP pre-compile and Apache I have the precompiled JSP's working with Apache now. Thanks. Apart from the first-time-hit compilation penalty on a normal jsp (as apposed to a precompiled one), why would you choose one option above the other? Standard jsp is easier to do updates if you work in an unpacked war setup - you just change the file and it is updated. Precompiled you have to acctually precompile the file. But how about performance and other issues? I guess it depends on your application, but is there somewhere a good checklist to determine when to choose the one option over the other? --- Terence M. Bandoian [EMAIL PROTECTED] wrote: Have you granted the site accessClassInPackage runtime permission? -Terence M. Bandoian [EMAIL PROTECTED] I used to precompile my JSP's (which worked great and was a big time saver in testing), but since running Tomcat 4.1.31 together with Apache, all sorts of weird errors occurred. I remember reading somewhere that Apache expected the actual jsp file, not the compiled version. So I reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone managed to get precompiled JSP's running in combination with Apache? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: JSP pre-compile and Apache
With all due respect, I find that a weak argument. Its pretty dangerous to deploy anything to production without testing it on another (local) environment first. I would never change a jsp on production without checking it on another environment first. Well there is one big advantage when using precompiled JSPs: You're sure that all JSPs are compilable, so you don't get any compile errors on your live site. That gives your application more stability. Bernhard -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. Juni 2005 08:07 An: Tomcat Users List Betreff: Re: JSP pre-compile and Apache I have the precompiled JSP's working with Apache now. Thanks. Apart from the first-time-hit compilation penalty on a normal jsp (as apposed to a precompiled one), why would you choose one option above the other? Standard jsp is easier to do updates if you work in an unpacked war setup - you just change the file and it is updated. Precompiled you have to acctually precompile the file. But how about performance and other issues? I guess it depends on your application, but is there somewhere a good checklist to determine when to choose the one option over the other? --- Terence M. Bandoian [EMAIL PROTECTED] wrote: Have you granted the site accessClassInPackage runtime permission? -Terence M. Bandoian [EMAIL PROTECTED] I used to precompile my JSP's (which worked great and was a big time saver in testing), but since running Tomcat 4.1.31 together with Apache, all sorts of weird errors occurred. I remember reading somewhere that Apache expected the actual jsp file, not the compiled version. So I reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone managed to get precompiled JSP's running in combination with Apache? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: JSP pre-compile and Apache
It's not that it's not tested. It can happen very easiliy, when you just forgot to check something in the version control: You added a method to a bean, change the JSP, it's working fine in you test environment, you check in the JSP, but forget the bean, do the release and you get the compile error on the live site. That can't happen with precompliation. -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. Juni 2005 10:28 An: Tomcat Users List Betreff: Re: AW: JSP pre-compile and Apache With all due respect, I find that a weak argument. Its pretty dangerous to deploy anything to production without testing it on another (local) environment first. I would never change a jsp on production without checking it on another environment first. Well there is one big advantage when using precompiled JSPs: You're sure that all JSPs are compilable, so you don't get any compile errors on your live site. That gives your application more stability. Bernhard -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. Juni 2005 08:07 An: Tomcat Users List Betreff: Re: JSP pre-compile and Apache I have the precompiled JSP's working with Apache now. Thanks. Apart from the first-time-hit compilation penalty on a normal jsp (as apposed to a precompiled one), why would you choose one option above the other? Standard jsp is easier to do updates if you work in an unpacked war setup - you just change the file and it is updated. Precompiled you have to acctually precompile the file. But how about performance and other issues? I guess it depends on your application, but is there somewhere a good checklist to determine when to choose the one option over the other? --- Terence M. Bandoian [EMAIL PROTECTED] wrote: Have you granted the site accessClassInPackage runtime permission? -Terence M. Bandoian [EMAIL PROTECTED] I used to precompile my JSP's (which worked great and was a big time saver in testing), but since running Tomcat 4.1.31 together with Apache, all sorts of weird errors occurred. I remember reading somewhere that Apache expected the actual jsp file, not the compiled version. So I reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone managed to get precompiled JSP's running in combination with Apache? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
