Hi, I was having the same problem; a good workaround for me was to edit
web.xml to insert "old style" configuration:
<context-param> <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> <param-value>com.sun.facelets.FaceletViewHandler</param-value> </context-param> <filter> <display-name>Ajax4jsf Filter</display-name> <filter-name>ajax4jsf</filter-name> <filter-class>org.ajax4jsf.FastFilter</filter-class> <init-param> <param-name>enable-cache</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>forceparser</param-name> <param-value>false</param-value> </init-param> </filter> <filter-mapping> <filter-name>ajax4jsf</filter-name> <url-pattern>*.seam</url-pattern> </filter-mapping>
Maybe they documented but didn't implement it yet?
Conversation filter isn't working either.
Ajax4JSF filter and mappings are mentioned in this Seam 2.0 Migration Guide.
Seam Team, isn't it necessary to add the Migration Guide (from 1.2.1.GA) to the Seam 2.0 Reference Guide?
I had already read the migration guide.
That's why I am saying "old style" configuration; maybe I've just messed up some jars.
thanks, I'm going to look again at it... still when using the web.xml to configure it it gives me no problems at all.