Disabling empty-element tag generation in jsp (pre)compilation
Hi, i am using Jasper coming with tomcat 4.1.31 for precompilation of some jsps. It generates empty-element tags where generation of start-tag followed by immediate end-tag would be needed/preferred. For example there are includes like: jsp:include page=includes/scripts.jsp/ where scripts.jsp contains the lines like script type=text/javascript src=lib/whatever.js /script. Precompiled jsps output these in their shortened form: script type=text/javascript src=lib/whatever.js/. How do i tune that behaviour - jasper options, jsps themselves, xml parser? thanks, Taimo
Re: Disabling empty-element tag generation in jsp (pre)compilation
Hi, You could do: script ...///script So the parser won't see an empty element. (and you will see your XHTML rendered in the browser) best, -Rob Taimo Peelo wrote: Hi, i am using Jasper coming with tomcat 4.1.31 for precompilation of some jsps. It generates empty-element tags where generation of start-tag followed by immediate end-tag would be needed/preferred. For example there are includes like: jsp:include page=includes/scripts.jsp/ where scripts.jsp contains the lines like script type=text/javascript src=lib/whatever.js /script. Precompiled jsps output these in their shortened form: script type=text/javascript src=lib/whatever.js/. How do i tune that behaviour - jasper options, jsps themselves, xml parser? thanks, Taimo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jsp Pre-compilation
Yeboo,
The pathes needed to be absolute. Thanks for the help. Sorry for the late
reply.
Gruss
Nils
mtgglf
-Original Message-
From: Bernhard Slominski [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 3:18 PM
To: 'Tomcat Users List'
Subject: AW: Jsp Pre-compilation
Hi Nils,
two things:
1. I would use an absolute path instead of the realitive one ./hummingbird
I guess jasper just can't pick up your jsps!
2. outputDir: You set it to WEB-INF/classes but what you create are
actually java source files, so this is not right, even tohough it doesn't
explain the failure of the precompliation
Good luck
Bernhard
-Ursprüngliche Nachricht-
Von: Nils Liebelt [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 30. Juni 2005 15:09
An: tomcat-user@jakarta.apache.org
Cc: [EMAIL PROTECTED]
Betreff: Jsp Pre-compilation
Hi all,
I have trouble pre-compiling my jsp-pages. I wrote following
ant target:
target name=jspc depends=build
taskdef classname=org.apache.jasper.JspC name=jasper2
classpath id=jspc.classpath
fileset dir=${tomcat.home}/bin
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/server/lib
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/common/lib
include name=*.jar/
/fileset
/classpath
/taskdef
jasper2 validateXml=false
compile=true
verbose=99
listErrors=true
uriroot=./hummingbird
webXmlFragment=./hummingbird/WEB-INF/generated_web.xml
outputDir=./hummingbird/WEB-INF/classes /
/target
The task executes successful but it does not create a single
java file nor
its outputs anything? I want execute the task out of my
project src folder.
The libraries should be at the right place. I am really stuck here...
Regards,
Nils
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jsp Pre-compilation
Hi all,
I have trouble pre-compiling my jsp-pages. I wrote following ant target:
target name=jspc depends=build
taskdef classname=org.apache.jasper.JspC name=jasper2
classpath id=jspc.classpath
fileset dir=${tomcat.home}/bin
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/server/lib
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/common/lib
include name=*.jar/
/fileset
/classpath
/taskdef
jasper2 validateXml=false
compile=true
verbose=99
listErrors=true
uriroot=./hummingbird
webXmlFragment=./hummingbird/WEB-INF/generated_web.xml
outputDir=./hummingbird/WEB-INF/classes /
/target
The task executes successful but it does not create a single java file nor
its outputs anything? I want execute the task out of my project src folder.
The libraries should be at the right place. I am really stuck here...
Regards,
Nils
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: Jsp Pre-compilation
Hi Nils,
two things:
1. I would use an absolute path instead of the realitive one ./hummingbird
I guess jasper just can't pick up your jsps!
2. outputDir: You set it to WEB-INF/classes but what you create are
actually java source files, so this is not right, even tohough it doesn't
explain the failure of the precompliation
Good luck
Bernhard
-Ursprüngliche Nachricht-
Von: Nils Liebelt [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 30. Juni 2005 15:09
An: tomcat-user@jakarta.apache.org
Cc: [EMAIL PROTECTED]
Betreff: Jsp Pre-compilation
Hi all,
I have trouble pre-compiling my jsp-pages. I wrote following
ant target:
target name=jspc depends=build
taskdef classname=org.apache.jasper.JspC name=jasper2
classpath id=jspc.classpath
fileset dir=${tomcat.home}/bin
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/server/lib
include name=*.jar/
/fileset
fileset dir=${tomcat.home}/common/lib
include name=*.jar/
/fileset
/classpath
/taskdef
jasper2 validateXml=false
compile=true
verbose=99
listErrors=true
uriroot=./hummingbird
webXmlFragment=./hummingbird/WEB-INF/generated_web.xml
outputDir=./hummingbird/WEB-INF/classes /
/target
The task executes successful but it does not create a single
java file nor
its outputs anything? I want execute the task out of my
project src folder.
The libraries should be at the right place. I am really stuck here...
Regards,
Nils
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
tomcat 4.1.x jsp pre-compilation
hi, when i pre-compile my jsps, i found that Tomcat only likes them when they are compiled with the package org.apache.jsp. if i change the generated *_jsp.java files (before compiling) to a different package that is anything but org.apache.jsp, Tomcat fails to load them when I try to access the page. Tomcat (4.1.x) seems to have hard-coded logic inside to only work with jsp class files packaged under org.apache.jsp. has anyone found a workaround for this, so that we are not restricted to compile all jsp's to the package org.apache.jsp? is this a setting/configuration we can tweak on Tomcat? thanks in advance!! __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 4.1.x jsp pre-compilation
Hi Woodchuck,
I just fought the exact same thing for two weeks and
this is what I discovered:
If you want to precompile all the JSPs with a package
name other than org.apache.jsp you have to use the -p
option and give it a new package name. This doesn't
really work, as you may have already discovered,
especially if you want the subdirectories the JSPs
exist under to be included in the package name. To
get the sub-dirs included I wrote a script to find all
the JSPs under my app's root dir then walked through
the list and submitted a jspc compile for each of the
JSPs in the list. I computed the package name based
on the sub-directory the JSP was found in. Here's the
main loop I used for my script:
# Begin Code -
ALL_JSP_FILES=`find ${WEBAPP_ROOT_DIR}/${PRODUCT}/*
-name '*.jsp'`
for i in ${ALL_JSP_FILES}
do
echo Compiling $i
JSP_FILE=${i##*/}
#echo JSP_FILE = $JSP_FILE
# JSP_DIR is just an intermediate directory that
# doesn't need to be passed on to the next
# script (i.e. doesn't need to be exported).
JSP_DIR=${i%/*}
#echo JSP_DIR = $JSP_DIR
PRODUCT_SUB_DIR=${JSP_DIR#*/${PRODUCT}}
#echo PRODUCT_SUB_DIR = $PRODUCT_SUB_DIR
# We have to source this script in order
# for the exported variables to still be
# valid. (i.e. put the . in front of it)
. compile_single_jsp.sh
done
# End Code
The compile_single_jsp.sh converts the PRODUCT_SUB_DIR
variable to a dotted package name suffix using sed:
PACKAGE_SUFFIX=`echo $PRODUCT_SUB_DIR | sed -e
's/\//./g'`
and then calls jspc.sh to do the actual compile:
jspc.sh \
-v4 \
-l \
-compile \
-d
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}/WEB-INF/classes
\
-p com.mycompany${PACKAGE_SUFFIX} \
-webinc
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}${PRODUCT_SUB_DIR}/${JSP_FILE}.xml
\
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}${PRODUCT_SUB_DIR}/${JSP_FILE}
I run this from the /bin directory in my tomcat root.
The downside to this is that you then have to merge
all of the individual web.xml fragments produced by
each compile into the existing web.xml (or a brand new
one you create). I wrote another script and then a
C++ program to do this.
The only way around this is to use Tomcat 5.x to do
the compile. It will automatically compute the
package name with subdirs though I still had to submit
each by hand to get it to compile beyond my root
directory (I'm still looking into this). Of course
you can't run these compiled JSPs under anything but
Tomcat 5.x so it's kind of useless if you are stuck
back at 4.x. I had to move to 5.x because of a bug in
the 4.x jspc compiler that produced 0 length .java
files on an compile error but didn't tell you what the
error was. So currently I use jspc from Tomcat 5.0.25
but still merge all the xml fragments after the
compiles complete. It sucks, but the code is already
written so I'm sticking with it until I have time to
find another way.
Hope that helps,
Jason
--- Woodchuck [EMAIL PROTECTED] wrote:
hi,
when i pre-compile my jsps, i found that Tomcat only
likes them when they are compiled with the package
org.apache.jsp.
if i change the generated *_jsp.java files (before
compiling) to a different package that is anything
but
org.apache.jsp, Tomcat fails to load them when I
try
to access the page.
Tomcat (4.1.x) seems to have hard-coded logic inside
to only work with jsp class files packaged under
org.apache.jsp.
has anyone found a workaround for this, so that we
are
not restricted to compile all jsp's to the package
org.apache.jsp?
is this a setting/configuration we can tweak on
Tomcat?
thanks in advance!!
__
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 4.1.x jsp pre-compilation
hi Jason,
thx a lot for your reply. i am, unfortunately, stuck
with Tomcat 4.1.x.
i don't have any problems getting jspc to generate
.java files for jsps that exist in a hierarchical
(sp?) tree. for instance, my jsps are scattered under
my web root folder, in sub folders, etc..
my problem is that Tomcat 4.1.x only seems to work
with .class files that were compiled into the
org.apache.jsp package. as a result, i have to do
the following round-about deployment:
1) invoke jspc to generate .java files for all .jsps
2) modify each resulting .java file to have the
following first line: package org.apache.jsp;
3) invoke javac to compile the .java into .class
4) place .class files into same hierarchy as the
original .jsps
if i were using Tomcat 5 like you were i would only
have to do steps 1 and 3 above and i'm done.
the caveat here is that each .jsp is assumed to have a
unique name. if not, javac will let you know with a
compile-time error, and you will have to compile
multiple times (each time a subset of unique .java
classes that are outputted to its own folder, then
place every .class file back into respective hierarchy
after all compilation is done). this is what i'm
seeking to avoid doing.
anyhow, i appreciate your help, but i'm not sure if
it's applicable to my situation. the jspc compiler
i'm using will automatically take the jsp's location
into account and compute the corresponding package
suffix.
--- Jason Palmatier [EMAIL PROTECTED] wrote:
Hi Woodchuck,
I just fought the exact same thing for two weeks and
this is what I discovered:
If you want to precompile all the JSPs with a
package
name other than org.apache.jsp you have to use the
-p
option and give it a new package name. This doesn't
really work, as you may have already discovered,
especially if you want the subdirectories the JSPs
exist under to be included in the package name. To
get the sub-dirs included I wrote a script to find
all
the JSPs under my app's root dir then walked through
the list and submitted a jspc compile for each of
the
JSPs in the list. I computed the package name based
on the sub-directory the JSP was found in. Here's
the
main loop I used for my script:
# Begin Code -
ALL_JSP_FILES=`find ${WEBAPP_ROOT_DIR}/${PRODUCT}/*
-name '*.jsp'`
for i in ${ALL_JSP_FILES}
do
echo Compiling $i
JSP_FILE=${i##*/}
#echo JSP_FILE = $JSP_FILE
# JSP_DIR is just an intermediate directory that
# doesn't need to be passed on to the next
# script (i.e. doesn't need to be exported).
JSP_DIR=${i%/*}
#echo JSP_DIR = $JSP_DIR
PRODUCT_SUB_DIR=${JSP_DIR#*/${PRODUCT}}
#echo PRODUCT_SUB_DIR = $PRODUCT_SUB_DIR
# We have to source this script in order
# for the exported variables to still be
# valid. (i.e. put the . in front of it)
. compile_single_jsp.sh
done
# End Code
The compile_single_jsp.sh converts the
PRODUCT_SUB_DIR
variable to a dotted package name suffix using sed:
PACKAGE_SUFFIX=`echo $PRODUCT_SUB_DIR | sed -e
's/\//./g'`
and then calls jspc.sh to do the actual compile:
jspc.sh \
-v4 \
-l \
-compile \
-d
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}/WEB-INF/classes
\
-p com.mycompany${PACKAGE_SUFFIX} \
-webinc
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}${PRODUCT_SUB_DIR}/${JSP_FILE}.xml
\
${TOMCAT_ROOT_DIR}/webapps/${PRODUCT}${PRODUCT_SUB_DIR}/${JSP_FILE}
I run this from the /bin directory in my tomcat
root.
The downside to this is that you then have to merge
all of the individual web.xml fragments produced by
each compile into the existing web.xml (or a brand
new
one you create). I wrote another script and then a
C++ program to do this.
The only way around this is to use Tomcat 5.x to do
the compile. It will automatically compute the
package name with subdirs though I still had to
submit
each by hand to get it to compile beyond my root
directory (I'm still looking into this). Of course
you can't run these compiled JSPs under anything but
Tomcat 5.x so it's kind of useless if you are stuck
back at 4.x. I had to move to 5.x because of a bug
in
the 4.x jspc compiler that produced 0 length .java
files on an compile error but didn't tell you what
the
error was. So currently I use jspc from Tomcat
5.0.25
but still merge all the xml fragments after the
compiles complete. It sucks, but the code is
already
written so I'm sticking with it until I have time to
find another way.
Hope that helps,
Jason
--- Woodchuck [EMAIL PROTECTED] wrote:
hi,
when i pre-compile my jsps, i found that Tomcat
only
likes them when they are compiled with the package
org.apache.jsp.
if i change the generated *_jsp.java files (before
compiling) to a different package that is anything
but
org.apache.jsp, Tomcat fails to load them when I
try
to access the page.
Tomcat (4.1.x) seems to have
Re: war deployment and jsp pre-compilation
Thanks, but that's not the problem. I know how to use Ant and jspc. The question is whether/how I can tell Tomcat to load pre-compiled JSPs from my war file which is not unpacked as I deploy with unpackWars set to false. Any ideas? Reinhard Johannes Fiala wrote: Hi Reinhard, Using TC 4.1.24+ you can use ant to first run JspC and deploy the resulting WAR using the manager app. You can find more info here: http://www.fwd.at/tomcat/buildmanagement-using-ant-howto.html Johannes Reinhard Nägele [EMAIL PROTECTED] 10.07.2003 15:38 Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject war deployment and jsp pre-compilation We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war deployment and jsp pre-compilation
At 11:05 AM 7/11/2003 +0200, you wrote: Thanks, but that's not the problem. I know how to use Ant and jspc. The question is whether/how I can tell Tomcat to load pre-compiled JSPs from my war file which is not unpacked as I deploy with unpackWars set to false. The work directory is Tomcat's temp directory. It is the one place that is guaranteed to allow files to be written for a webapp. It has nothing to do with your issue. Actually, I'm not really sure what you are talking about. Precompiled jsp's added to the webapp are just servlets. You don't need to use File IO to load servlets. They should be able to run out of a .war file just as they can from a directory. You specify this using servlet and servlet-mapping entries in in web.xml just like any other servlet. Are you saying that this works for you when the .war is unpacked, but not when it isn't? That would be truly odd. you'll need to explain why you think things aren't working from a .war file first before anyone can help you here. Jake Any ideas? Reinhard Johannes Fiala wrote: Hi Reinhard, Using TC 4.1.24+ you can use ant to first run JspC and deploy the resulting WAR using the manager app. You can find more info here: http://www.fwd.at/tomcat/buildmanagement-using-ant-howto.html Johannes Reinhard Nägele [EMAIL PROTECTED] 10.07.2003 15:38 Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject war deployment and jsp pre-compilation We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war deployment and jsp pre-compilation
I'm afraid, I wasn't clear enough explaining the issue. First, let's assume, I do not pre-compile my JSPs and deploy the war with the manager app. Upon the first request, Tomcat will go about and compile the JSPs to the working directory. As there is no context entry in the server.xml, Tomcat will use its default working directory. Now, I'd like to pre-compile the JSPs including only the compiled JSP classes in the war file. This means that Tomcat would have to load the JSP classes directly from the war file instead of from its working directory. Can this be done? I hope the issue is clear now. Thanks for any insight. Reinhard Jacob Kjome wrote: At 11:05 AM 7/11/2003 +0200, you wrote: Thanks, but that's not the problem. I know how to use Ant and jspc. The question is whether/how I can tell Tomcat to load pre-compiled JSPs from my war file which is not unpacked as I deploy with unpackWars set to false. The work directory is Tomcat's temp directory. It is the one place that is guaranteed to allow files to be written for a webapp. It has nothing to do with your issue. Actually, I'm not really sure what you are talking about. Precompiled jsp's added to the webapp are just servlets. You don't need to use File IO to load servlets. They should be able to run out of a .war file just as they can from a directory. You specify this using servlet and servlet-mapping entries in in web.xml just like any other servlet. Are you saying that this works for you when the .war is unpacked, but not when it isn't? That would be truly odd. you'll need to explain why you think things aren't working from a .war file first before anyone can help you here. Jake Any ideas? Reinhard Johannes Fiala wrote: Hi Reinhard, Using TC 4.1.24+ you can use ant to first run JspC and deploy the resulting WAR using the manager app. You can find more info here: http://www.fwd.at/tomcat/buildmanagement-using-ant-howto.html Johannes Reinhard Nägele [EMAIL PROTECTED] 10.07.2003 15:38 Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject war deployment and jsp pre-compilation We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war deployment and jsp pre-compilation
At 02:40 PM 7/11/2003 +0200, you wrote: I'm afraid, I wasn't clear enough explaining the issue. First, let's assume, I do not pre-compile my JSPs and deploy the war with the manager app. Upon the first request, Tomcat will go about and compile the JSPs to the working directory. As there is no context entry in the server.xml, Tomcat will use its default working directory. Now, I'd like to pre-compile the JSPs including only the compiled JSP classes in the war file. This means that Tomcat would have to load the JSP classes directly from the war file instead of from its working directory. Can this be done? I hope the issue is clear now. Yes, again, pre-compled jsp file are servlets. They don't get compiled at runtime, again, because they are servlets. You now have to register and map them in the web.xml just like any other servlet. If by pre-compiling, you mean run some script which accesses each jsp file at runtime so that when a real human accesses them they will already be compiled, then you don't have to worry about the mapping. Actually, you should never have to worry about the work directory stuff. Tomcat will use a work directory whether or not an app is deployed from a .war file or directory. Which work directory is not of the app's concern, but of Tomcat's. You are going to have to explain exactly where you think this whole thing will fail when running from a .war file because it is still not clear to me. Jake Thanks for any insight. Reinhard Jacob Kjome wrote: At 11:05 AM 7/11/2003 +0200, you wrote: Thanks, but that's not the problem. I know how to use Ant and jspc. The question is whether/how I can tell Tomcat to load pre-compiled JSPs from my war file which is not unpacked as I deploy with unpackWars set to false. The work directory is Tomcat's temp directory. It is the one place that is guaranteed to allow files to be written for a webapp. It has nothing to do with your issue. Actually, I'm not really sure what you are talking about. Precompiled jsp's added to the webapp are just servlets. You don't need to use File IO to load servlets. They should be able to run out of a .war file just as they can from a directory. You specify this using servlet and servlet-mapping entries in in web.xml just like any other servlet. Are you saying that this works for you when the .war is unpacked, but not when it isn't? That would be truly odd. you'll need to explain why you think things aren't working from a .war file first before anyone can help you here. Jake Any ideas? Reinhard Johannes Fiala wrote: Hi Reinhard, Using TC 4.1.24+ you can use ant to first run JspC and deploy the resulting WAR using the manager app. You can find more info here: http://www.fwd.at/tomcat/buildmanagement-using-ant-howto.html Johannes Reinhard Nägele [EMAIL PROTECTED] 10.07.2003 15:38 Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject war deployment and jsp pre-compilation We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
war deployment and jsp pre-compilation
We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war deployment and jsp pre-compilation
Hi Reinhard, Using TC 4.1.24+ you can use ant to first run JspC and deploy the resulting WAR using the manager app. You can find more info here: http://www.fwd.at/tomcat/buildmanagement-using-ant-howto.html Johannes Reinhard Nägele [EMAIL PROTECTED] 10.07.2003 15:38 Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject war deployment and jsp pre-compilation We deploy our application as war file with the manager. unpackWars is set to false. Is it possible to deploy pre-compiled JSPs with this approach? I guess this would imply that we'd have to have a context.xml in our war file specifying that Tomcat should load the compiled JSP classes from the war file instead of from its working directory. Can this be done? Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
