You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-user@tomcat.apache.org by Martin Cooper <ma...@tumbleweed.com> on 2002/04/22 06:21:34 UTC
Using JSTL with Resin 2.0.5 and Tomcat 4.0.3
So I have two puzzles now.
I've been using JSTL (Beta 2) with Resin 2.0.5. Things seem to work in
general. I just copied all the jar files into my WEB-INF/lib, wrote some
JSP, and it worked. Until, that is, I tried <c:forEach>. It doesn't seem to
matter what flavour of collection I pass in 'items', it only ever gives me
the first item. I figured this might be a problem with Resin, so...
I tried running the same web app under Tomcat 4.0.3. Same directory
structure - I just copied the whole thing over from Resin. But I don't even
get off the ground with Tomcat. At the first access to a page, I get the
following exception message from Jasper:
"This absolute uri (http://java.sun.com/jstl/core) cannot be resolved in
either web.xml or the jar files deployed with this application"
Now, I don't have anything in my web.xml (I didn't even have one,
initially), but I know for a fact that the JSTL TLD files are in
standard.jar, which is in my WEB-INF/lib. Tomcat (or rather, Jasper) doesn't
seem to be able to find them.
Anyone have any bright ideas on how I can get one or other (and preferably
both) of these containers to play ball with JSTL?
Thanks!
--
Martin Cooper
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Using JSTL with Resin 2.0.5 and Tomcat 4.0.3
Posted by Ryan Lubke <Ry...@Sun.COM>.
Yes this is a bug in 4.0.3 (6400 I think). The workaround is to create a
directory called 'temp' in CATALINA_HOME
mkdir $CATALINA_HOME/temp.
-rl
On Sun, 2002-04-21 at 23:45, Shawn Bayern wrote:
> Martin,
>
> I believe you're hitting two entirely different bugs, one in Resin and one
> in Tomcat. The Resin issue is, I believe, a known bug in 2.0.5; my
> impression was that there is a later release that addresses the issue.
> Tomcat 4.0.3 indeed looks like it fails to sense TLD files automatically.
>
> I believe Tomcat 4.0.4B2 (the most recent milestone release for Tomcat)
> addresses this issue, so I think upgrading is the solution in both cases.
> Or, if you want to use Tomcat 4.0.3, you should be able to do so by
> modifying web.xml to refer to the tag libraries explicitly.
>
> --
> Shawn Bayern
> "JSP Standard Tag Library" http://www.jstlbook.com
> (coming this summer from Manning Publications)
>
> On Sun, 21 Apr 2002, Martin Cooper wrote:
>
> > So I have two puzzles now.
> >
> > I've been using JSTL (Beta 2) with Resin 2.0.5. Things seem to work in
> > general. I just copied all the jar files into my WEB-INF/lib, wrote some
> > JSP, and it worked. Until, that is, I tried <c:forEach>. It doesn't seem to
> > matter what flavour of collection I pass in 'items', it only ever gives me
> > the first item. I figured this might be a problem with Resin, so...
> >
> > I tried running the same web app under Tomcat 4.0.3. Same directory
> > structure - I just copied the whole thing over from Resin. But I don't even
> > get off the ground with Tomcat. At the first access to a page, I get the
> > following exception message from Jasper:
> >
> > "This absolute uri (http://java.sun.com/jstl/core) cannot be resolved in
> > either web.xml or the jar files deployed with this application"
> >
> > Now, I don't have anything in my web.xml (I didn't even have one,
> > initially), but I know for a fact that the JSTL TLD files are in
> > standard.jar, which is in my WEB-INF/lib. Tomcat (or rather, Jasper) doesn't
> > seem to be able to find them.
> >
> > Anyone have any bright ideas on how I can get one or other (and preferably
> > both) of these containers to play ball with JSTL?
> >
> > Thanks!
> >
> > --
> > Martin Cooper
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Using JSTL with Resin 2.0.5 and Tomcat 4.0.3
Posted by Martin Cooper <ma...@tumbleweed.com>.
Shawn,
Thanks! You're right on both counts. I've upgraded to Resin 2.1.0 and Tomcat
4.0.4-b2, and they're both working just fine.
--
Martin Cooper
----- Original Message -----
From: "Shawn Bayern" <ba...@essentially.net>
To: "Tag Libraries Users List" <ta...@jakarta.apache.org>
Sent: Sunday, April 21, 2002 9:45 PM
Subject: Re: Using JSTL with Resin 2.0.5 and Tomcat 4.0.3
> Martin,
>
> I believe you're hitting two entirely different bugs, one in Resin and one
> in Tomcat. The Resin issue is, I believe, a known bug in 2.0.5; my
> impression was that there is a later release that addresses the issue.
> Tomcat 4.0.3 indeed looks like it fails to sense TLD files automatically.
>
> I believe Tomcat 4.0.4B2 (the most recent milestone release for Tomcat)
> addresses this issue, so I think upgrading is the solution in both cases.
> Or, if you want to use Tomcat 4.0.3, you should be able to do so by
> modifying web.xml to refer to the tag libraries explicitly.
>
> --
> Shawn Bayern
> "JSP Standard Tag Library" http://www.jstlbook.com
> (coming this summer from Manning Publications)
>
> On Sun, 21 Apr 2002, Martin Cooper wrote:
>
> > So I have two puzzles now.
> >
> > I've been using JSTL (Beta 2) with Resin 2.0.5. Things seem to work in
> > general. I just copied all the jar files into my WEB-INF/lib, wrote some
> > JSP, and it worked. Until, that is, I tried <c:forEach>. It doesn't seem
to
> > matter what flavour of collection I pass in 'items', it only ever gives
me
> > the first item. I figured this might be a problem with Resin, so...
> >
> > I tried running the same web app under Tomcat 4.0.3. Same directory
> > structure - I just copied the whole thing over from Resin. But I don't
even
> > get off the ground with Tomcat. At the first access to a page, I get the
> > following exception message from Jasper:
> >
> > "This absolute uri (http://java.sun.com/jstl/core) cannot be resolved in
> > either web.xml or the jar files deployed with this application"
> >
> > Now, I don't have anything in my web.xml (I didn't even have one,
> > initially), but I know for a fact that the JSTL TLD files are in
> > standard.jar, which is in my WEB-INF/lib. Tomcat (or rather, Jasper)
doesn't
> > seem to be able to find them.
> >
> > Anyone have any bright ideas on how I can get one or other (and
preferably
> > both) of these containers to play ball with JSTL?
> >
> > Thanks!
> >
> > --
> > Martin Cooper
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Using JSTL with Resin 2.0.5 and Tomcat 4.0.3
Posted by Shawn Bayern <ba...@essentially.net>.
Martin,
I believe you're hitting two entirely different bugs, one in Resin and one
in Tomcat. The Resin issue is, I believe, a known bug in 2.0.5; my
impression was that there is a later release that addresses the issue.
Tomcat 4.0.3 indeed looks like it fails to sense TLD files automatically.
I believe Tomcat 4.0.4B2 (the most recent milestone release for Tomcat)
addresses this issue, so I think upgrading is the solution in both cases.
Or, if you want to use Tomcat 4.0.3, you should be able to do so by
modifying web.xml to refer to the tag libraries explicitly.
--
Shawn Bayern
"JSP Standard Tag Library" http://www.jstlbook.com
(coming this summer from Manning Publications)
On Sun, 21 Apr 2002, Martin Cooper wrote:
> So I have two puzzles now.
>
> I've been using JSTL (Beta 2) with Resin 2.0.5. Things seem to work in
> general. I just copied all the jar files into my WEB-INF/lib, wrote some
> JSP, and it worked. Until, that is, I tried <c:forEach>. It doesn't seem to
> matter what flavour of collection I pass in 'items', it only ever gives me
> the first item. I figured this might be a problem with Resin, so...
>
> I tried running the same web app under Tomcat 4.0.3. Same directory
> structure - I just copied the whole thing over from Resin. But I don't even
> get off the ground with Tomcat. At the first access to a page, I get the
> following exception message from Jasper:
>
> "This absolute uri (http://java.sun.com/jstl/core) cannot be resolved in
> either web.xml or the jar files deployed with this application"
>
> Now, I don't have anything in my web.xml (I didn't even have one,
> initially), but I know for a fact that the JSTL TLD files are in
> standard.jar, which is in my WEB-INF/lib. Tomcat (or rather, Jasper) doesn't
> seem to be able to find them.
>
> Anyone have any bright ideas on how I can get one or other (and preferably
> both) of these containers to play ball with JSTL?
>
> Thanks!
>
> --
> Martin Cooper
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>