That's exactly what I meant by writing: > the main purpose of jspc is to get rid of your jsp-files since it > simply converts them to servlet (and generates the correct > servlet-config for your web.xml).
Sorry, if I wasn't clear enough on that point. Jspc generates the corresponding java-classes and the servlet mapping for your web-xml as well, if you want. But what I (and others perhaps) need, is to precompile the jsps at startup *AND* deploy the jsp-source. The advantage of deploying the jsp-source is to be able to make short corrections in a fast way (spelling mistakes and things - really a common and not an abstract case) without redeploying everything and restarting the server (because I would not run a production server with a reloadable context - performance issues). So I would like to precompile all jsps at startup and want the tomcat to recompile changed jsps. That's not possible with jspc. And thus, I would love to see (and implement if I find the right "hook" :) such a feature - if others find it useful too... pero > -----Original Message----- > From: Tom Drake [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 15, 2001 9:52 PM > To: Tomcat Users List > Subject: Re: Precompile JSP > > > Not true. You can deploy your pre-compiled jsp's in the > form of java classes. There is no need to deploy jsp source > code. You'll need to make corresponding mapping > entries in your web.xml, however. > > ----- Original Message ----- > From: "pero" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Thursday, November 15, 2001 12:07 PM > Subject: RE: Precompile JSP > > > | Note: Jspc doesn't compile your jsps as the webserver would do. > That means > | that when you call jspc and start the server afterwards then > the webserver > | will compile the jsps itselft again (at least this is my experience). I > | think the main purpose of jspc is to get rid of your jsp-files since it > | simply converts them to servlet (and generates the correct > servlet-config > | for your web.xml). Another solution to simply compile a jsp is > to call it > | (from a browser) with the jsp_precompile=true parameter (example: > | http://localhost:8080/my.jsp?jsp_precompile=true) Then the jsp will be > | compiled but NOT executed. > | I simply wrote a servlet that goes through the whole web-app > and calls all > | jsps this way. > | The Java-Code to call one jsp would be: > | > | URL url = new URL ("http://localhost:8080/my.jsp?jsp_precompile=true";); > | URLConnection con = url.openConnection(); > | con.getInputStream(); > | > | Hope this helps (or at least adds another point of view to the > discussion) > | > | pero > | > | > -----Original Message----- > | > From: Tom Parker [mailto:[EMAIL PROTECTED]] > | > Sent: Thursday, November 15, 2001 8:54 PM > | > To: Tomcat Users List; Tom Drake > | > Subject: RE: Precompile JSP > | > > | > > | > > Try bin/jspc.bat or jspc.sh > | > > | > I would like to compile my jsp's as a test before I deploy it and > | > see if it > | > works. I spend quite a lot of time changing stuff, deploying, > loading in > a > | > web browser and seeing jsp compiliation problems. > | > > | > It would be nice to have jspc compile my jsp's during the deployment > | > process. I tried this and it seems to recompile everything, > | > rather than only > | > those files that have changed. > | > > | > Is there a depends option to jspc? > | > > | > The obvious solution is to use ant to only compile those > files that have > | > changed, but there doesn't seem to be an equivelent of make's > | > .c.o option in > | > ant. Is there a dependset creator anywhere, if there isn't a generic > .c.o > | > type task? > | > > | > > | > -- > | > To unsubscribe: <mailto:[EMAIL PROTECTED]> > | > For additional commands: <mailto:[EMAIL PROTECTED]> > | > Troubles with the list: <mailto:[EMAIL PROTECTED]> > | > > | > > | > | > | -- > | To unsubscribe: <mailto:[EMAIL PROTECTED]> > | For additional commands: <mailto:[EMAIL PROTECTED]> > | Troubles with the list: <mailto:[EMAIL PROTECTED]> > | > | > | > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
