[richfaces-issues] [JBoss JIRA] (RF-13590) ajaxRendered does not work if f:ajax is used
Daniel Lechner (JIRA)
issues at jboss.org
Wed Mar 26 04:11:13 EDT 2014
[ https://issues.jboss.org/browse/RF-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Lechner updated RF-13590:
--------------------------------
Attachment: ajaxDemo.xhtml
DummyBean.java
> ajaxRendered does not work if f:ajax is used
> --------------------------------------------
>
> Key: RF-13590
> URL: https://issues.jboss.org/browse/RF-13590
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.5
> Environment: Wildfly 8.0.0.Final
> Reporter: Daniel Lechner
> Labels: ajax, jsf22
> Attachments: ajaxDemo.xhtml, DummyBean.java
>
>
> The component {{a4j:outputPanel}} offers the attribute {{ajaxRendered}} which should update the contents of the panel at every ajax request (see Chapter 2 of the Component Reference). But on a small testpage which is attached, this can easily be disproved.
> When using the first spinner of the example (which uses {{f:ajax}}), the new value gets submitted into the model, but the {{outputPanel}} is not rerendered. If I use the second one (with the {{a4j:ajax}} inside), everything works as expected.
> This effect is the same e.g. for {{a4j:commandButton}} vs. {{h:commandButton}} + {{f:ajax}} and other constellations.
> I would expect (especially when reading the reference) that the panel is rerendered even in the {{f:ajax}} case.
> Additional note: In contrast to this, the status-indicator works for all ajax requests, nevertheless if it is raised by an RichFaces component or {{f:ajax}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list