There are some people that would like to precompile the webapp and then
just deploy the generated servlets with there webapp, to remove this
option would really hinder their ability to due this (although the
package naming already makes this tough to do and there are patches
floating around to
Indeed, I'm one of those persons. I generate the web.xml
fragment for my entire webapp, and integrate it into my
original web.xml using xslt. I deploy only the generated
servlets, no JSP or Java sources at all.
It would be really bad if I couldn't do that anymore.
-- Sebastian
[EMAIL
Hi Remy,
being another toyer I believe your second point is
covered by the --compile flag. What I personally lack
is the possibility to get warnings when compiling.
(As opposed to errors only.)
Grüsse,
Michael
-Original Message-
From: Remy Maucherat [mailto:remm;apache.org]
Sent:
Although I'm just a user, I would like to warnings also. On a related
note, --compile isn't covered in the documentation. I stumbled across
it when I look at the source code a month back. It might be nice to
output the warnings to a file for those who have large webapps with
thousands of jsp
Remy Maucherat wrote:
Hi all,
I toyed a bit with the webapp option of JSPC, and a few things seemed
really odd.
- Although there are options to generate web.xml files or fragments,
this makes no sense as the generated files are now meant to be put in
the work directory instead. This was
peter lin wrote:
Although I'm just a user, I would like to warnings also. On a related
note, --compile isn't covered in the documentation. I stumbled across
it when I look at the source code a month back. It might be nice to
output the warnings to a file for those who have large webapps with
