pre-compilation of JSP

[Saritha Pula <sp...@SonicWALL.com>]

hi all,
  I am working on pre-compilation of JSP 
But problem for me is when I type the following command
jspc -webxml c:\web.xml -uriroot c:\cosmo\jsp -webapp example.jsp
the above command automatically generates "web.xml"  but with "no
contents in it"
Java file is "not generated" for the specified JSP

it would be greatful if I can get some inputs on this
Pula

-----Original Message-----
From: Randy Layman [mailto:randy.layman@aswethink.com]
Sent: Tuesday, July 10, 2001 9:50 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: using pre-compiled JSPs



	I like it for two reasons:
	1.  Performance
	2.  Don't need to distribute JavaC with the application

	The drawbacks as I see it:
	1.  Recompiling the JSPs generally works better than updating
servlets for getting an update out while the server is running
	2.  There isn't currently any good way of merging the generated
web.xml file with your web.xml file.  (Making automated builds relies on
inserting some special token to your web.xml file in order to do the
merge,
or requires building a process that reads your web.xml file, knows where
the
other xml file goes, and performs the merge for you).
	3.  It can be confusing for new developers who don't quite
understand that file.jsp is really being handled by a servlet and that's
why
their changes to the file.jsp file are not seeming to take affect.

	Randy


> -----Original Message-----
> From: Eitan Ben-Noach [mailto:Eitanb@proficiency.com]
> Sent: Tuesday, July 10, 2001 12:19 PM
> To: tomcat-user@jakarta.apache.org
> Subject: using pre-compiled JSPs
> 
> 
> Hello,
> 
> I would like to know whether pre-compiled JSPs is a 
> conventional way for
> deploying JSPs at the customers sites? Are there any 
> disadvantages with
> this approach?
> 
> Thanks,
> 
> Eitan Ben-Noach
>