Hey KC,
Just checked the 1.0 spec and it doesn't look like it. Also, the other jakarta taglibs
don't seem to support this. It is of course possible to do this yourself using the
c:out tag. What you described can be rewritten to:
c: out
Hello,
I am facing a problem while starting tomcat with struts and JSTL. I read all the mail
for reply to your mail in the taglibs-user list. But was more confused. Can you please
help me to recetify the problem.
I am getting the same error which you got.
org.xml.sax.SAXParseException:
On apache site there are two down loads for standard tag libs .
standad and standard 1.0 whats the difference between these two .
Thanks and Regards
Deepak
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Hey Deepak,
Looks like you have a taglibrary in there somewhere that has an incorrect or missing
!DOCTYPE declaration in it's tld file. The DOCTYPE is required to be correct by the
XML parser so it can check if you have the syntax of your XML-file(in your case
tld-file) correct.
Grtz,
Martin
I'm cross-posting this problem that I've already sent
to the Tomcat users list, without success. I'm having
that problem with a JSTL app failing under Tomcat
4.0.6. The error is No such tag redirect in the tag
library imported with prefix c. I get a single line
in the stderr.log: No tags.
The
OK, maybe I'll do that. Since URLs seem to have so much variability, I
was hoping that someone else had already written some bulletproof code.
K.C.
Martin van Dijken wrote:
Hey KC,
Just checked the 1.0 spec and it doesn't look like it. Also, the other jakarta taglibs don't seem to support
Sorry to be a dirty cross-poster.
Yoav Shapiro has provided me with hope. When I told
him I was running Tomcat 4.0.6 as a Windows service,
he suggested that I shut it down and start Tomcat on
the command line using startup.bat.
When I did that, the app that was failing came right
up
I upgraded to tomcat 5 and taglib standard 1.0.4. In my deployment
descriptor I replaced the old web-app_2_3.dtd reference with
web-app_2_4.xsd . Now I'm having problems.
What was working fine:
fmt:message key=${var4SomeKey}/
is now causing the JasperException:
According to TLD or attribute
You should probably try using Standard 1.1.0-B1 since TC 5 is a JSP 2.0
container. Note that the URI will be different:
JSTL 1.0:
http://java.sun.com/jstl/fmt
JSTL 1.1:
http://java.sun.com/jsp/jstl/fmt
Quoting Adam Hardy [EMAIL PROTECTED]:
I upgraded to tomcat 5 and taglib standard 1.0.4. In
deepaksawdekar wrote:
On apache site there are two down loads for standard tag libs .
standad and standard 1.0 whats the difference between these two .
If you click on each one of those links, the answer is right there.
And to understand the difference between JSTL 1.0 and JSTL 1.1,
please check
I had wanted to do that but had stupidly not found the tarball. I got it
now but after deploying them and changing the taglib declares to what
you gave, tomcat chokes on the TLD validation. Do you recognise the
problem?
preRegister with Catalina:type=Logger,path=/blacksail,host=localhost
I really haven't played around with TC 5 or JSTL 1.1, but a quick smoke test
passed just fine. I used the following JSP:
%@ page contentType=text/plain %
%@ taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
%@ taglib prefix=fmt uri=http://java.sun.com/jsp/jstl/fmt; %
c:set var=key
I included my jsp below.
All I have to do though to trigger the exceptions (about 10) is to
include the standard-1.1.0-B1.jar in my webapp. I think it must be
related to something in my web.xml. I'm using the following now since I
upgraded to web-app_2_4:
jsp-config
jsp-property-group
Sorry, I'm struggling with this a bit. There's alot going on in tomcat5
that I'm not sure about yet.
It's caching the tld files which I didn't realise, so I had to add a bit
to my deploy script.
It seems like I'm getting a different error with every change I make.
Basically I get the error
Adam Hardy wrote:
Sorry, I'm struggling with this a bit. There's alot going on in tomcat5
that I'm not sure about yet.
It's caching the tld files which I didn't realise, so I had to add a bit
to my deploy script.
It seems like I'm getting a different error with every change I make.
Basically
15 matches
Mail list logo
