----- Original Message ---- > From: Wes Wannemacher <w...@wantii.com> > To: Struts Users Mailing List <user@struts.apache.org> > Sent: Thursday, September 3, 2009 7:18:06 AM > Subject: Re: possible bug in v2.1.6 ?? > > I'm pretty sure the problem is that by default tomcat only maps *.jsp > to the jsp servlet. You can try to setup an extra servlet mapping in > your web.xml, but if you can use .jsp instead of .jspf, you're > probably better off. > > You are right, it is a convention to use .jspf (for JSP Fragment), but > it looks like Tomcat devs forgot about that one ;) > > -Wes > >
Hi Wes, Why then does it work with Servlet+JSP+JSTL1.2 on the same exact dev system? I'd would agree with you if it fails with just the basics. Thanks, Tommy > On Thu, Sep 3, 2009 at 9:58 AM, Tommy Phamwrote: > > > > Hi Wes, > > > > Thank you very much for fast response and solution to my problem (didn't > > think > about trying with this). Yes, changing from jspf to jsp works as desired. > Is > my implementation wrong? I remember reading somewhere (I can't remember > where) > that by convention, jsp fragments should be used with extension .jspf and > placed > inside /WEB-INF/jspf/*.jspf where my jspf files are located currently. > > > > Thanks, > > Tommy > > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
