I'm not sure why it would be treated as an external context, but it
seems both the RI and MyFaces are treating it as such. The only thing I
can think of if that's the case would be to prefix the path with the
application context, which would be painful if I wanted to deploy the
app to a differe
The reason maybe JavaServer Face treating "/pages/projects/Projects.faces"
as an external context so whenever /pages/projects/Projects.faces is called,
com.sun.faces.context.ExternalContextImpl will doForward, however, since it
is included in Tiles Tag, and resposne is committed, you got the except
Correction: the problem occurs when I change a nested tile to .faces
instead of .jsp. Changing *only* the containing layout tile's definition
seems to work. However, I have to include f:view in the nested JSP;
including it in the layout doesn't seem to be sufficient, which makes me
think using
I'm trying to get JSF working in my Struts app using the struts-faces
integration library. I have everything set up per the readme that comes
with struts-faces. I can successfully load foo.jsp with the URL
foo.faces, so I think things are configured correctly.
However, as soon as I change the d
4 matches
Mail list logo
