myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Heinen <>
Subject pages not rendered anymore after update from 1.1.6 to 1.2.8
Date Tue, 08 Dec 2009 14:13:54 GMT

I tried to update my webApp from myfaces 1.1.6, tomahawk 1.1.7 and richfaces 3.1.5 to JSF
After some problems the webapp finally started but no page is rendered anymore.
Instead of the pages I get only empty screens without any content at all!

I am still using Tiles1 (from struts1.1jar) in combination with jsps and not Facelets.

What I did:
1) Updated myFaces jars from 1.1.6 to 1.2.8 (api and impl)
2) updated tomahawk 1.1.7 to tomahawk12-1.1.9
3) removed tomhahawk sandbox 1.1.7
4) updated richfaces from 3.1.5 to 3.3.2 (api,impl and ui)
5) updated jstl-1.1.0.jar to jstl-1.2.jar and removed standard.jar
6) deleted work folder of the webApp
7) updated faces-config.xml: set version attribute of faces-config tag to version="1.2"
8) updated web.xml: set version attribute of web-app tag version="2.5"

I attached the initialization log and the request log with debugging output.
Initialization looks good from my point of view.

One suspicious line in the request.log:
 [2009-12-08 14:45:17,492] http-8080-1 [ WARN] [D57992BA5C47A836C0EBE03C0224EB3B] webapp.BaseFilter
checkMyFacesExtensionsFilter: MyFaces Extensions Filter should be configured to execute *AFTER*
RichFaces filter. Refer to SRV.6.2.4 section of Servlets specification on how to achieve that.

The order of the filters in web.xml is not changed and Faces Extensions Filter IS AFTER richfaces
    <servlet-name>Faces Servlet</servlet-name>


I don't know whether the problem is caused, by MyFaces, Richfaces, Tomhawk Tiles or whatever
at the moment.
Any idea where to look at?


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message