What about using external entities?
ie:
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
[
!ENTITY jspservlet system jspservlet.xml
]
then, between the servlet and servlet
On Fri, 21 Mar 2003, Remy Maucherat wrote:
Date: Fri, 21 Mar 2003 12:05:26 +0100
From: Remy Maucherat [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: [5.0] [PROPOSAL] Extra web.xml to declare compiled JSPs
Hi,
Craig R. McClanahan wrote:
Many app servers have private deployment descriptors for extra
information, similar to what Remy is proposing -- indeed, one could claim
that Tomcat does this already with how we use $CATALINA_HOME/conf/web.xml
to set default behavior (well, at least until Costin's
-Original Message-
From: Chris Brown [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 6:43 AM
To: Tomcat Developers List
Subject: Re: [5.0] [PROPOSAL] Extra web.xml to declare compiled JSPs
Hi Remy,
It might be worth COPYING the original web.xml at deployment
time, to make
John Trollinger wrote:
Remy,
I think it would be nice to have a pre-compilier like JspC used to be.
The precompile part of the jsp spec is just not that handy when trying
to do builds and having ant tasks pass or fail based on the jsp and
compiling jsp pages into servelts is not an option for
Remy Maucherat wrote:
Hi,
It is not very convinient or easy to insert the declarations for
compiled JSPs into the webapp's web.xml file. It also has the
disadvantage of adding a lot of mess in the web.xml, which the user may
not like.
For that reason, I propose that Tomcat parses a new
Costin Manolache wrote:
Remy Maucherat wrote:
Hi,
It is not very convinient or easy to insert the declarations for
compiled JSPs into the webapp's web.xml file. It also has the
disadvantage of adding a lot of mess in the web.xml, which the user may
not like.
For that reason, I propose that
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Friday, March 21, 2003 3:05 AM
Subject: [5.0] [PROPOSAL] Extra web.xml to declare compiled JSPs
Hi,
It is not very convinient or easy to insert the declarations for
Could an alternate hack be to modify JspServlet to allow an additional
init parameter which would be the file which contains the mapping of the
precompiled jsp's? The config file could just be the web.xml snippet
generated by the precompilation process. This way web.xml isn't touched
and if
The main point is to _not_ hack anything, but just use the standard.
If you precompile your app - and include jasper-runtime.jar in WEB-INF/lib -
the result should work in _any_ container - the precompiled jsps are _just_
regular servlets that happen to use a lib and extend from a base class.
Costin Manolache wrote:
The main point is to _not_ hack anything, but just use the standard.
If you precompile your app - and include jasper-runtime.jar in WEB-INF/lib -
the result should work in _any_ container - the precompiled jsps are _just_
regular servlets that happen to use a lib and
Remy Maucherat wrote:
I agree that using ant replace is a hack - the right solution would be to
read the XML with DOM, insert the elements in the right place, and save
back ( DOM - so we don't loose comments ). Or even read it as a file, and
use regexp. No problem if we save the original
Remy Maucherat wrote:
Costin Manolache wrote:
The main point is to _not_ hack anything, but just use the standard.
If you precompile your app - and include jasper-runtime.jar in
WEB-INF/lib - the result should work in _any_ container - the precompiled
jsps are _just_ regular servlets that
Costin Manolache wrote:
Remy Maucherat wrote:
I don't know.
jasper-compiler is needed only to support development use cases, it
obviously shouldn't be used on production servers.
We are mixing 2 very different use cases here:
- development - you don't need to precompile and jasper-compiler is
14 matches
Mail list logo
