List of issues to take into account when migrating from 1.0.9m9 to 1.1.0:
- If you like to use the myfaces-all.jar, there is a show stopper bug in the 1.1.0 which make it unusuable if you want to use myfaces components. Use the three jars instead (myfaces-api.jar, myfaces-impl.jar, tomahawk.jar)
Now, you can ommit the context listener setup (the <listener> entry) from the web.xml, because now it is included in the tld (as the RI does). However, this might not work in every container.
Just in case such an error occurs, it is perfectly viable to add the entry, even if it is already defined in the jar files.
the correct entry has to look like:
<listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener> <!-- Faces Servlet --> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet>
Just before the first servlet entry the filter entry has to be defined...
Container problems with <listener> inside of tld instead of web.xml
- Jetty 5.1.3 (via the Eclipse jetty launcher plugin)