My bet would be that the .jspf extension is not mapped to be processed by the JSP Processor in your Servlet Container. I think .jspf is just a naming convention, it doesn't have any intrinsic meaning to the container, so if you want to continue putting your fragments in .jsp files, they should work fine. (*Chris*)
On Wed, Jul 14, 2010 at 12:08 PM, Ken <ken.mcwilli...@aerose.com> wrote: > The following is in a file called "menu.jspf" > > <%@ page pageEncoding="UTF-8" %> > <%@ taglib prefix="s" uri="/struts-tags" %> > <h2>Menu</h2> > <s:a action="login">Login</s:a> > > The html produced is (produces <s:a> tags instead of <a> tags...): > <h2>menu</h2> > <s:a action="login">Login</s:a > > The exact same code is now placed in a file called "menu.jsp" and it > produces (the expected result)... > <h2>menu</h2> > <a href="/MZWEB/login">Login</a> > > I am using Netbeans 6.9 RC2 with Glassfish Prelude... What's causing > this? I've never used jspf files before, but they have less template > code in them, where the jsp files are templated for a new web page > (meta, head, body...). So I thought jspf are just "fragments" the exact > same behaviour but made to assemble pages... anyways I see no issue > using jsp files with my tiles but was just wondering what this was > about. >
