Hello,
I have installed Jakarta Tomcat 4.1.24 and Jakarta Taglibs 1.0.3,
both of which support the JSP specification. I found the README
file /usr/local/jakarta-taglibs/standard-1.0.3/README to be
close to useless: it seems to me that copying the files
standard-doc.war and standard-examples.war
Hello,
I have a tag that begins with c:out ...
When I run Jasper by loading the page I get the JSP error:
org.apache.jasper.JasperException:
/hello.jsp(9,16) Unable to load class out
[...snip...]
Any ideas of what is wrong (tomcat 4.1.24 and taglibs 1.0.3)?
It seems something with my
Have you configured the taglib in your web.xml using
taglib element ?
--- Neil Zanella [EMAIL PROTECTED]
Hello,
I have installed Jakarta Tomcat 4.1.24 and Jakarta
Taglibs 1.0.3,
both of which support the JSP specification. I found
the README
file
On Sun, 29 Jun 2003, [gb2312] guo yingshou wrote:
Have you configured the taglib in your web.xml using
taglib element ?
No I have not because:
1. I have not seen anything about this in the documentation.
2. I have read that Tomcat 4.1.24 has an autodetection feature
which makes this
Have a look at servlet specification.
--- Neil Zanella [EMAIL PROTECTED]
On Sun, 29 Jun 2003, [gb2312] guo yingshou wrote:
Have you configured the taglib in your web.xml
using
taglib element ?
No I have not because:
1. I have not seen anything about this in the
documentation.
Well, I just had a look at the instructions at:
http://jakarta.apache.org/taglibs/doc/standard-doc/standard/GettingStarted.html
and they say to copy the contents of directory:
/usr/local/jakarta-taglibs/standard-1.0.3/lib
to the WEB-INF/lib directory. That worked, but
once again, it seems
Actually, step 3. is unnecessary. When you create the
JAR file for your handler, the TLD file goes inside
it. It's already got the URI string you should use in
your JSP. When the JSP compiler goes looking for your
TLD, it'll find it in the JAR because it's already in
the CLASSPATH.
That's
On Sun, 29 Jun 2003, Michael Duffy wrote:
Actually, step 3. is unnecessary. When you create the JAR file for
your handler, the TLD file goes inside it. It's already got the URI
string you should use in your JSP. When the JSP compiler goes looking
for your TLD, it'll find it in the JAR
Are you sure it works on all j2ee complaint servlet
engine?
thanks.
--- Michael Duffy [EMAIL PROTECTED]
Actually, step 3. is unnecessary. When you create
the
JAR file for your handler, the TLD file goes inside
it. It's already got the URI string you should use
in
your JSP. When the
On Mon, 30 Jun 2003, [gb2312] guo yingshou wrote:
Are you sure it works on all j2ee complaint servlet engine?
The behavior is mandated by sections 7.2.1 and 7.3.1 of the JSP 1.2
specification, so all compliant containers support it; if a product
claiming compliance doesn't support it, then it's
Thanks for your info. I never do that before.Maybe I
need to have a detailed look at the sections you
mentions if I have time later.After a glimpse of these
lines,a question pops up my mind:
If it is *mandatory*,why the web-app.dtd still
specifiy an optional taglib element?Just for backward
11 matches
Mail list logo
