[
http://jira.jboss.com/jira/browse/JBSEAM-498?page=comments#action_12347000 ]
Reind D commented on JBSEAM-498:
--------------------------------
I did look at the A4J documentation under Seam support but missed the mention of facelets
support. And I did look at the Booking example and noticed the absence of the
<view-handler> in the faces-config.xml which is what prompted me to consider this
issue.
Anyway, here's the relevant section in case anyone else is interested:
https://ajax4jsf.dev.java.net/nonav/documentation/ajax-documentation/deve...
For example, the declaration:
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
says that Facelets will officially be first, however AjaxViewHandler will sneak a little
ahead temporarily to do some small, but very important, job. (Note: you do not define
FaceletViewHandler in the WEB-INF/faces-config.xml.)
SeamFaceletViewHandler causes Ajax4jsf a4j:outputPanel reRender
attribute to be skipped
---------------------------------------------------------------------------------------
Key: JBSEAM-498
URL:
http://jira.jboss.com/jira/browse/JBSEAM-498
Project: JBoss Seam
Issue Type: Bug
Environment: JBoss 4.0.5, JSF RI 1.2.03
Reporter: Reind D
If you add SeamFaceletViewHandler to a Seam app that uses ajax4jsf the a4j:outputPanel
reRender attribute stops working. Removing the view handler restores functionality. A4J
still works if you use add ajaxRendered="true" to an outputPanel though.
<application>
<view-handler>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</view-handler>
...
</application>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira