Well... I don't gonna keep in mind the third option... obviously obvious
isn't it ? ;-)
Probably we gonna keep our previous method to precompile JSPs unless I
find out an efficient and quick method to set it up.
Le 09/07/2007 15:54, David Delbecq a écrit :
You can either precompile (eg using specific tomcat ant target) and
include the precompiled files in your .war, add with it the mappings in
web.xml for each jsp. (Long and not so easy)
Or,
you can install in tomcat something like lambda-probe, that has an
interface to compile JSP, interface you could use after deployement to
compile all JSPS
Or,
you can simple not precompile...
En l'instant précis du 09/07/07 15:50, Phi-Long LE s'exprimait en ces
termes:
hi there,
currently, the project I work on, we deploy our application simply
using tar file, now testing tomcat, we would use war file... that's ok
for that.... in a meantime on our current production platform
(iplanet) we precompile JSP and create an other tar file... what is
then the best practise using tomcat ?
should we create a war file including precompiled jsp or should we
deploy the Webapp using Tomcat and then precompile JSP ? what is the
most efficient way ?
any help or advice would be really appreciated,
Phi-Long
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
