This content has been marked as final.
Show 6 replies
-
1. Re: Ajax4jsf Filter --> I go wild page
gavin.king Mar 1, 2007 11:08 AM (in response to rengar)The filter runs tidy on your HTML. So if your HTML is not clean XHTML, you might get some funny changes..
-
2. Re: Ajax4jsf Filter --> I go wild page
rengar Mar 1, 2007 12:01 PM (in response to rengar)I use facelets and XHTML.
-
3. Re: Ajax4jsf Filter --> I go wild page
sergeysmirnov Mar 1, 2007 3:41 PM (in response to rengar)add forceparser as an init param set to false
i.e. :
<display-name>Ajax4jsf Filter</display-name>
<filter-name>ajax4jsf</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
<init-param>
<param-name>forceparser</param-name>
<param-value>false</param-value>
</init-param>
<filter-mapping>
also, add to the filter mapping the following lines:
REQUEST
FORWARD
INCLUDE -
4. Re: Ajax4jsf Filter --> I go wild page
sergeysmirnov Mar 1, 2007 3:43 PM (in response to rengar)for filter mapping:
<dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher>
-
5. Re: Ajax4jsf Filter --> I go wild page
svadu Mar 1, 2007 6:19 PM (in response to rengar)Btw, the seam examples don't use the dispatcher tags in the ajax4jsf configurations...
-
6. Re: Ajax4jsf Filter --> I go wild page
rengar Mar 2, 2007 4:23 AM (in response to rengar)Ok, this is the solution.
Now the application works fine.
Thanks.