-
1. Re: Ajax4JSF and Facelets
sergeysmirnov Aug 29, 2007 4:48 PM (in response to ericomtx)may be you have no filter declared in the web.xml
-
2. Re: Ajax4JSF and Facelets
ericomtx Aug 29, 2007 5:01 PM (in response to ericomtx)<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletsViewHandler</param-value>
</context-param>
<display-name>Ajax4jsf Filter</display-name>
<filter-name>ajax4jsf</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
<filter-mapping>
<filter-name>ajax4jsf</filter-name>
<url-pattern>*.jsf</url-pattern>
REQUEST
FORWARD
INCLUDE
</filter-mapping>
I have other filters from shale and MyFaces declared in my web.xml
Could one of them or their properties as mapping intervene in ajax4jsf filter ? -
3. Re: Ajax4JSF and Facelets
sergeysmirnov Aug 29, 2007 5:16 PM (in response to ericomtx)In general, "A4J is not defined" means the javascript is not loaded. The script is generated by filter. For myFaces, you need to have a a4j:page tag declared right after f:view. If you do not, it might be the problem. You declare that only *.jsf are comes thru the filter. So, if the particular pages does not, it also might be the problem.
The earlier version of shale used to have bug that causes the problem of integration. However, I did not see about any conflict for long period of time.
Search the Internet for the proven web.xml declaration. If I remember correctly, MyFaces wiki has something like that. -
4. Re: Ajax4JSF and Facelets
ericomtx Aug 31, 2007 3:36 PM (in response to ericomtx)The problem was the integration with Shale
I was using the 1.0.4 and changed to 1.0.3 as you said
It's working ok now
Thanks !!!