Petr Jiricka wrote:
Remy Maucherat wrote:
Jan Luehe wrote:
Currently, if webapp developers do not want to expose the source of
their JSP files, they have to precompile them and add a servlet
mapping for each JSP to their web.xml (e.g., with the help of jspc).
If the webapp contains a large number
Remy Maucherat wrote:
Jan Luehe wrote:
Currently, if webapp developers do not want to expose the source of
their JSP files, they have to precompile them and add a servlet
mapping for each JSP to their web.xml (e.g., with the help of jspc).
If the webapp contains a large number of JSPs, the web.xml
Jan Luehe wrote:
Tim Funk wrote:
How will phantom pages be addressed? Pages where the jsp once existed
but then was deleted, but the corresponding class was not deleted?
That's why I suggested an option for JspServlet that would disable this
"optimization" and require a servlet mapping for eac
Tim Funk wrote:
How will phantom pages be addressed? Pages where the jsp once existed
but then was deleted, but the corresponding class was not deleted?
That's why I suggested an option for JspServlet that would disable this
"optimization" and require a servlet mapping for each precompiled JSP.
Jan Luehe wrote:
Currently, if webapp developers do not want to expose the source of
their JSP files, they have to precompile them and add a servlet
mapping for each JSP to their web.xml (e.g., with the help of jspc).
If the webapp contains a large number of JSPs, the web.xml is going to
grow pret
How will phantom pages be addressed? Pages where the jsp once existed but
then was deleted, but the corresponding class was not deleted?
-Tim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
