I stand corrected; my usual gaffe in this area is missing an end tag, which is quite a bit different as you correctly point out from an extra end tag.
> -----Original Message----- > From: Shawn Bayern [mailto:bayern@;essentially.net] > Sent: Wednesday, October 30, 2002 11:40 AM > To: Tag Libraries Users List > Subject: RE: multiple </x:if> > > > On Wed, 30 Oct 2002, Gideon, Thomas wrote: > > > It looks to me like you have a syntactic error, one too many closing > > </c:if> tags. Which version of JSTL are you using? 1.02, at least > > for the core library, is better about catching an un-matched end tag > > during translation. Perhaps there is a bug in the xml > taglib, but you > > can easily work around it be correcting your JSP. > > Catching mismatched tags is not the function of JSTL; it's done > automatically by the container, and version 1.0.2 shouldn't be any > different in this regard from 1.0.1. Please let me know if > you've indeed > noticed otherwise. Any mismatched tags should be caught > correctly by the > container for the Standard Taglib 1.0.1. > > But indeed, you are correct that dangling "end" tags will simply be > printed out by a JSP container. This behavior is appropriate > per the JSP > specification; under the non-XML syntax, an unmatched </x:if> tag is > simply template text. > > -- > Shawn Bayern > "JSTL in Action" http://www.jstlbook.com > > > -- > To unsubscribe, e-mail: > <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:taglibs-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
