For what it¹s worth I was getting some strange results with included jspfs. In my case it was the freemarker encoding that was getting screwed up.
What I found was if I included the <%@ page contentType="text/html;charset=UTF-8" language="java" %> tag at the head of my .jspf files it worked fine. I don¹t know if it was a tomcat or struts issue but I know that now all our .jspf files include the tag. And we haven¹t seen the problem again. Z. > > On Thu, Sep 3, 2009 at 10:35 AM, Tommy Pham<tommy...@yahoo.com> wrote: >> > >> > 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 >> > > > To be honest I don't know, my guess is that since the original request > comes in through the jsp servlet, it "just works" whereas the struts > filter catches the request and eventually dispatches to the JSP. I'm > sure if I read the spec and mapped this out as a use-case, there is > probably a logical reason, but I just figured that if you can rename > the fragments, then you are better off... Another thought, instead of > using fragments, have you thought about using tag files? I quit using > includes as soon as the .tag files became available. > > -Wes
