Bernhard Slominski wrote:
Hi,
after getting the jsp precompilation finally working, I want also want to do
the precompliation for tag files.
JSP precompilation should also trigger precompilation for custom tags
within the JSP.
The precompilation task generates servlets and servlet mappings
David Smith schrieb:
Just a thought:
Last I knew using the j2ee jar w/ Tomcat == EVIL. You can either use
the j2ee distribution on Sun's site OR Jakarta Tomcat (w/ j2sdk, not
j2ee), but never j2ee and jakarta tomcat together. It'll create some
really ugly version conflicts. If you use
Are you sure you want
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c%
and not
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
-Tim
Marcus Beyer wrote:
Hello all!
I am trying to precompile my JSPs using org.apache.jasper.JspC.
Problem: The ones that use JSTL result in
Tim Funk schrieb:
Are you sure you want
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c%
and not
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
Oh, right. Thank you!
Unfortunately the error persists nevertheless ...
--
Grüße, Marcus
http://www.Stormlight.de
Whatever you do will
Tim Funk schrieb:
Are you sure you want
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c%
and not
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
-Tim
c:if test=${true}
c:out value=this is JSTL :) /
/c:if
Strange. After changing to JSTL 1.1 taglib, that c:if thing above
Tim Funk schrieb:
I finally solved my (first) problem: I had a wrong lib (J2EE 1.3) in my
class path. So there was some kind of version mismatch ...
Are you sure you want
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c%
and not
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
Geachte relatie,
Het door u gebruikte e-mailadres is niet meer actief. U kunt uw e-mailbericht
sturen naar [EMAIL PROTECTED] of dit bericht beantwoorden.
Bedankt voor uw medewerking,
Met vriendelijke groet,
ATP Hypotheken
Het Spoor 40
3994 AK Houten
Tel. 030 750 25 33
Fax. 030 750 25 88
Is your web.xml using the 2.4 declaration?
-Tim
Marcus Beyer wrote:
Tim Funk schrieb:
I finally solved my (first) problem: I had a wrong lib (J2EE 1.3) in my
class path. So there was some kind of version mismatch ...
Are you sure you want
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c%
Geachte relatie,
Het door u gebruikte e-mailadres is niet meer actief. U kunt uw e-mailbericht
sturen naar [EMAIL PROTECTED] of dit bericht beantwoorden.
Bedankt voor uw medewerking,
Met vriendelijke groet,
ATP Hypotheken
Het Spoor 40
3994 AK Houten
Tel. 030 750 25 33
Fax. 030 750 25 88
Just a thought:
Last I knew using the j2ee jar w/ Tomcat == EVIL. You can either use
the j2ee distribution on Sun's site OR Jakarta Tomcat (w/ j2sdk, not
j2ee), but never j2ee and jakarta tomcat together. It'll create some
really ugly version conflicts. If you use jakarta tomcat from
Tim Funk schrieb:
Is your web.xml using the 2.4 declaration?
Yes it is.
The problem has to do with precompilation, because it works if I deploy
the JSPs instead of the servlets.
Example: c:out value=1 + 2 = ${1 + 2} /
The precompiled Java code looks like this:
_jspx_th_c_out_1.setValue(new
Tim Funk schrieb:
Oops, my bad. Forget newInstance() being called. But the line:
Class bean = ctxt.getClassLoader().loadClass(klass);
I believe does force my previous static statements to hold true.
The problem was not during static initalizations but during
instantiation of the beans. I solved
Marcus Beyer schrieb:
Using Tomcat 5.0.26 I have some problems precompiling my pages with:
org.apache.jasper.JspC
The precompiler instantiates some beans, altough I don't exactly know
why. During instatiation some beans need to access managed beans, so
they call something like this:
There here, but your 1st post was a on a Friday afternoon. And the errors
were not very clear. Stack traces and a better description is probably in order.
-Tim
Marcus Beyer wrote:
Marcus Beyer schrieb:
Using Tomcat 5.0.26 I have some problems precompiling my pages with:
Tim Funk schrieb:
There here, but your 1st post was a on a Friday afternoon. And the
errors were not very clear. Stack traces and a better description is
probably in order.
I see :-)
=== description ===
I am using the ant script I found on page
Marcus Beyer schrieb:
=== description ===
I am using the ant script I found on page
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html.
Sorry, I mean this one:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html
Marcus
Ahh. Here is your issue:
if (beanName == null) {
try {
Class bean = ctxt.getClassLoader().loadClass(klass);
int modifiers = bean.getModifiers();
if (!Modifier.isPublic(modifiers) ||
Modifier.isInterface(modifiers) ||
Tim Funk schrieb:
Ahh. Here is your issue:
if (beanName == null) {
try {
Class bean = ctxt.getClassLoader().loadClass(klass);
int modifiers = bean.getModifiers();
if (!Modifier.isPublic(modifiers) ||
Modifier.isInterface(modifiers) ||
Oops, my bad. Forget newInstance() being called. But the line:
Class bean = ctxt.getClassLoader().loadClass(klass);
I believe does force my previous static statements to hold true.
-Tim
Marcus Beyer wrote:
Tim Funk schrieb:
Ahh. Here is your issue:
if (beanName == null) {
try {
Class
Marcus Beyer schrieb:
The precompiler instantiates some beans, altough I don't exactly know
why. During instatiation some beans need to access managed beans, so
they call something like this:
FacesContext facesContext = FacesContext.getCurrentInstance ( );
/*
* this happens
You need to use Jasper 2 whic is on the Tomcat 5 homepage. There is an Ant build file
that you need to run to do this .. the instructions are there.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html
ADC
-Original Message-
From: Niraj Alok [mailto:[EMAIL PROTECTED]
Sent:
There seem to be a number of differences between the runtime compiler and
the command line compiler (i.e. jspc which is called by ANT). One of them
being with file naming (the problem you describe). Also you will find that
if you have an underscore in the jsp file name both compilers will name
Mark,
Try to use -webinc option and include generated web.xml in the application's
deployment descriptor.
This will map all the generated Java classes to the corresponding JSP URLs.
Regards,
Rossen
-Original Message-
From: Mark O'Driscoll [mailto:[EMAIL PROTECTED]]
Sent: Monday,
23 matches
Mail list logo
