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
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
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
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
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
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
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
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
]
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
.
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
]
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
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
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
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
14 matches
Mail list logo
