Wow. Right on. Using the <web-app> with additional attributes as shown in the wiki entry below indeed solved the problem.
Thank you, and thanks to everyone else who patiently read my posts and offered help. Mark On 15Nov, Rahul Akolkar wrote: > On 11/15/05, Mark S Petrovic <[EMAIL PROTECTED]> wrote: > > I know I'll look back on this learning curve with a head-slapping > > recollection, but until then, for posterity: > > > > 1. If I remove the taglib directive in the JSP, the various <c:> tags > > are copied directly into the html output, with the browser doing its > > best to just ignore them. The plaintext tag body content is actually > > rendered, again, the result of the browser doing its best with what it > > considers unknown markup. > > > > 2. When I put the taglib directive back in, the JSP compiles and > > subsequently does something with the <c:> tag directives, as the tags are > > no longer copied into the resultant html and the default <c:otherwise> > > always seems to execute. Nor do I receive any exception output in the > > browser or in the catalina.out logfile. > > > > Whatever is misconfigured in my app is not a completely fatal situation: > > I just can't get at the scripting variables to do meaningful operations > > on them. > > > <snip/> > > Match JSTL to Servlet/JSP spec. You're using JSTL 1.1, and I suspect > you don't have a Servlet 2.4 web.xml. Some details are here [1]. > > -Rahul > > [1] http://wiki.apache.org/jakarta-taglibs/FrequentlyAskedQuestions > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Mark Petrovic Pasadena, CA USA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
