On 12/4/06, Scott Ferguson <[EMAIL PROTECTED]> wrote:
> On Dec 3, 2006, at 5:41 PM, Josh Rehman wrote:
> > 2) Adding this configuration doesn't fix the problem. The "doc"
> > attribute of x:parse is most certainly supported by JSTL 1.1:
> > http://java.sun.com/products/jsp/jstl/1.1/docs/tlddocs/index.html
> Which tag declaration are you using for the x:* tags?
<%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
> It looks like the @doc attribute is declared in Resin's 1.1 tld, but
> not the 1.0 tld. Also, Resin will use the jstl.jar if it's available
> (and fast-jstl is turned off) in preference to its own tag libraries.
I suggest that when a user disables fast-jstl and deploys a project
that uses JSTL and yet does not include the JSTL libraries (as I did
at first), that Resin should emit a warning, or possibly fail.
Abstractly, the first action is saying "Container, I'll take care of
this responsibility" - it would be nice if the container noticed that
the project really isn't taking care of the responsibility.
> -- Scott
> > -----
> > Interestingly, I just checked and realized that I had configured
> > Tomcat with JSTL at the container level, and so this project does not
> > contain the jstl.jar and standard.jar. I'm going to try adding these
> > next (and adding the taglib declaration to web.xml). But I see this as
> > a seperate bug in Resin: if I disable fast jstl, I would expect the
> > application to fail faster with a "taglib not found" type of error.
> > I am very much hoping that there is some oversight on my part. I do
> > not like JBoss's baroque configuration at all and would very much like
> > to convince my peers that Resin is the way to go.
> > Kind regards,
> > Josh Rehman
> > _______________________________________________
> > resin-interest mailing list
> > firstname.lastname@example.org
> > http://maillist.caucho.com/mailman/listinfo/resin-interest
> resin-interest mailing list
resin-interest mailing list