AW: AW: Load all JSP pages on startup
It's even better than that: the webapp itself is portable, without the
Tomcat libraries. The precompilation process just churns
your JSPs into
servlets at build time instead of runtime.
Let me add somthing here, it's right that the servlets are build at compile
time, but they still use Tomcat specific stuff.
Look at a generated servlet from a JSP:
...
public final class contactForm_jsp extends
org.apache.jasper.runtime.HttpJspBase
implements org.apache.jasper.runtime.JspSourceDependent {
...
As you see it uses Tomcat sepcific stuff, when running this webapp on a
different container you need the Tomcat libraries in your classpath!
Bernhard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: Load all JSP pages on startup
I don't want to precompile in my build script, With the precompilation you can do the stuff you need, it automatically creates the servlet mapping in the web.xml. The only thing you have to add is the load-on-startup1/load-on-startup part, but I think you can automate this as well. So why don't you want precompilation? Bernhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Load all JSP pages on startup
We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? Our application has to run on JBoss, Tomcat and Resin. Weblogic and others might be added in the future. I was hoping there was a simple way in the web deployment descriptor to load them all on startup, in a webserver independed way. Bernhard Slominski wrote: I don't want to precompile in my build script, With the precompilation you can do the stuff you need, it automatically creates the servlet mapping in the web.xml. The only thing you have to add is the load-on-startup1/load-on-startup part, but I think you can automate this as well. So why don't you want precompilation? Bernhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: Load all JSP pages on startup
We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? You're right precompliation is tomcat dependent, but it works like this that the ant task takes your (non-tomcat dependent) web.xml and just adds the mappings for the precompiled JSPs, so it would still be possible to use one single web.xml and then have a jsp server target-dependent precomplitation task, but I don't know how that works in resin or Weblogic, and I see your point now. Sorry, but I don't have a better solution for you! Bernhard I was hoping there was a simple way in the web deployment descriptor to load them all on startup, in a webserver independed way. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : AW: Load all JSP pages on startup
Hi, For WebLogic you can use: - ANT task (wlappc); - appc compiler; - setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor to configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up; -Message d'origine- De : Bernhard Slominski [mailto:[EMAIL PROTECTED] Envoyé : mercredi 29 juin 2005 15:40 À : 'Tomcat Users List' Objet : AW: AW: Load all JSP pages on startup We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? You're right precompliation is tomcat dependent, but it works like this that the ant task takes your (non-tomcat dependent) web.xml and just adds the mappings for the precompiled JSPs, so it would still be possible to use one single web.xml and then have a jsp server target-dependent precomplitation task, but I don't know how that works in resin or Weblogic, and I see your point now. Sorry, but I don't have a better solution for you! Bernhard I was hoping there was a simple way in the web deployment descriptor to load them all on startup, in a webserver independed way. - 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: RE : AW: Load all JSP pages on startup
- setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor to configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up; Can I do that on Tomcat too? :) Tomcat will ignore weblogic.xml and Weblogic will ignore jboss-web.xml, unlike Tomcat compiled JSP's in weblogic or visa versa. Thanks for any help, Geoffrey LERBSCHER Jean-Pierre wrote: Hi, For WebLogic you can use: - ANT task (wlappc); - appc compiler; - setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor to configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up; -Message d'origine- De : Bernhard Slominski [mailto:[EMAIL PROTECTED] Envoyé : mercredi 29 juin 2005 15:40 À : 'Tomcat Users List' Objet : AW: AW: Load all JSP pages on startup We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? You're right precompliation is tomcat dependent, but it works like this that the ant task takes your (non-tomcat dependent) web.xml and just adds the mappings for the precompiled JSPs, so it would still be possible to use one single web.xml and then have a jsp server target-dependent precomplitation task, but I don't know how that works in resin or Weblogic, and I see your point now. Sorry, but I don't have a better solution for you! Bernhard I was hoping there was a simple way in the web deployment descriptor to load them all on startup, in a webserver independed way. - 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: Load all JSP pages on startup
We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? You're right precompliation is tomcat dependent, but it works like this that the ant task takes your (non-tomcat dependent) web.xml and just adds the mappings for the precompiled JSPs, so it would still be possible to use one single web.xml and then have a jsp server target-dependent precomplitation task, but I don't know how that works in resin or Weblogic, and I see your point now. When thinking about it again I assume that the precompiled webapp with Tomcat should also work in any other JSP container, as long as you have the Tomcat libraries in your classpath, because in the end your compiled JSPs are just normal servlets. Bernhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : RE : AW: Load all JSP pages on startup
I think the simplest way is to write a custom ant task for each deployment (one for weblogic, another for tomcat et jboss). -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Geoffrey Envoyé : mercredi 29 juin 2005 16:29 À : tomcat-user@jakarta.apache.org Objet : Re: RE : AW: Load all JSP pages on startup - setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor to configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up; Can I do that on Tomcat too? :) Tomcat will ignore weblogic.xml and Weblogic will ignore jboss-web.xml, unlike Tomcat compiled JSP's in weblogic or visa versa. Thanks for any help, Geoffrey LERBSCHER Jean-Pierre wrote: Hi, For WebLogic you can use: - ANT task (wlappc); - appc compiler; - setting the precompile parameter to true in the jsp-descriptor element of the weblogic.xml deployment descriptor to configure WebLogic Server to precompile your JSPs when a Web Application is deployed or re-deployed or when WebLogic Server starts up; -Message d'origine- De : Bernhard Slominski [mailto:[EMAIL PROTECTED] Envoyé : mercredi 29 juin 2005 15:40 À : 'Tomcat Users List' Objet : AW: AW: Load all JSP pages on startup We have a custom (non-generated) web.xml, with some taglibs and servlets defined in there. Precompilation is tomcat dependend I suppose? You're right precompliation is tomcat dependent, but it works like this that the ant task takes your (non-tomcat dependent) web.xml and just adds the mappings for the precompiled JSPs, so it would still be possible to use one single web.xml and then have a jsp server target-dependent precomplitation task, but I don't know how that works in resin or Weblogic, and I see your point now. Sorry, but I don't have a better solution for you! Bernhard I was hoping there was a simple way in the web deployment descriptor to load them all on startup, in a webserver independed way. - 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: Load all JSP pages on startup
On Wed, Jun 29, 2005 at 04:49:10PM +0200, Bernhard Slominski wrote: : When thinking about it again I assume that the precompiled webapp with : Tomcat should also work in any other JSP container, as long as you have the : Tomcat libraries in your classpath, because in the end your compiled JSPs : are just normal servlets. It's even better than that: the webapp itself is portable, without the Tomcat libraries. The precompilation process just churns your JSPs into servlets at build time instead of runtime. (The container-specific precomps don't involve web.xml mappings for the generated servlets. That's why, for example, I can precomp in WebLogic and but still change my JSP on the fly. Maybe that's what you were thinking?) -and it's not as though you'd lose your custom web.xml configuration; there are ways to fold the generated servlet/mapping sets (from the JSP precomp) in with your original web.xml at build time. I don't have such an example readily available... there should be plenty in the archives, though. -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
