[
https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.s...
]
Andreas Hahne updated RF-13392:
-------------------------------
Workaround Description: In this situation, setting the attribute {{execute}} for
{{rich:tree}} to {{@this}} and specifing the {{rich:panel}}'s ID in the {{render}}
attribute solved the problem.
TreeSelectionChangeEvent always triggered during Apply Request Phase
--------------------------------------------------------------------
Key: RF-13392
URL:
https://issues.jboss.org/browse/RF-13392
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tree
Affects Versions: 4.3.3
Reporter: Andreas Hahne
Labels: richfaces, selectionChangeListener, tree
Fix For: 5-Tracking
Attachments: tree.zip
When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is
triggered during Apply Request Phase, no matter if the immediate attribute is set to true
or false.
This leads to a weird behaviour in our application where an output panel is filled with
the data selected in the tree. Both components are located in the same {{h:form}} element
(in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}}
component is updated correctly, the one in the {{h:inputText}} is not because it is
overwritten by the old value during Update Model Phase. If the change was processed during
Invoke Application Phase this would not occur most likely.
--
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