|
|
|
There is a suggested workaround here: http://wiki.opensymphony.com/display/WW/Problem+getting+SiteMesh+to+work+with+web.xml+errorPage
Has been committed. People using sitemesh will need to test their error pages to ensure that any workarounds still work.
Having this problem with cvs as of 2007.02.14 under Jetty 6.1.2pre1
We have the same problem in Grails (http://grails.org) however neither of the proposed solutions work. When debugging it seems that PageResponseWrapper sets sitemesh to abort when sendError is called on the response. This results in sitemesh never applying a layout.
I'm testing on Jetty 6. Any ideas? is there a release date proposed for 2.4 ? We're hitting this issue on tomcat6 and the proposed workaround from the wiki linked above doesn't work.
Darren,
Can you check out HEAD, and let me know if it solves your problem? http://www.opensymphony.com/sitemesh/cvs.action Cheers, Scott Hi Scott,
I get the same behaviour as I do in 2.3. With a 404 response code and the following web.xml stanzas, the page remains undecorated: <filter> <filter-name>sitemesh</filter-name> <filter-class>com.opensymphony.module.sitemesh.filter.PageFilter</filter-class> </filter> ... <filter-mapping> <filter-name>sitemesh</filter-name> <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>ERROR</dispatcher> </filter-mapping> ... <error-page> <error-code>404</error-code> <location>/WEB-INF/jsp/404.jsp</location> </error-page> Cheers, Darren Darren,
Can you attach a very simple war file that demonstrates your problem? That would make me sure that any solution I work on fixes your specific problem. Scott, attached is a .war that exhibits the same problem as I see in our project when running on Tomcat 6.0.14.
Cheers, just for completeness, my environment is:
OS: Linux 2.6.24 JDK: BEA jrockit-R27.4.0 SERVER: Tomcat 6..0.14 LIB: Sitemesh 2.4 SNAPSHOT compiled from CVS HEAD on 4/May/08 I haven't yet tested this myself - reopening the issue.
any news on this - even just to confirm as an issue to be resolved?
Haven't managed to confirm anything - just re-opened so that I'll look into it.
Does anyone know when 2.4 is going to be released into the maven repositories? We need this fix as well
| ||||||||||||||||||||||||||||||||||||||||||||
The funny thing is that my 403 page _does_ get decorated, while my 404 and 500 pages do not.