]
Jan Papousek commented on RF-11747:
-----------------------------------
I've tried to reproduce the bug, but I haven't been successful. I've created
the following a4j:jsFunction:
{code}
<h:outputLabel id="jsFunctionCheckerLabel" value="jsFunction
Checker" for="jsFunctionChecker"/>
<a4j:outputPanel id="jsFunctionChecker">
<h:outputText value="#{phasesBean.date}">
<f:convertDateTime pattern="HH:MM:ss.SSS" />
</h:outputText>
</a4j:outputPanel>
{code}
This function is called by '@onbeforetoggle' attribute and the date is rerendered
before the @toggleListener is invoked -> so the order of events holds.
RF 4.1 onbeforetoggle issue
---------------------------
Key: RF-11747
URL:
https://issues.jboss.org/browse/RF-11747
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-menu, regression
Affects Versions: 4.1.0.Milestone3, 4.1.0.Milestone4, 4.1.0.CR1
Environment: JDK 6, JSF 2, JBoss 6 Final
Reporter: Ibrahim Abu Ghosh
Assignee: Jan Papousek
Labels: richfaces
Dears,
i'am using rich:tree in two places, one in the main panel of my template, and the
other one is in a popup, i'am using the onbeforetoggle event, it was running
successfully since 4.0 to 4.1 M2, after M2 it is not functioning right, here is my tests
:
1- RF 4-M3, onbeforetoggle not firing in the main template & in the popup.
2- RF 4-M4, main template is firing the event, popup is not firing.
3- RF 4-CR1, same as M3.
here is my .xhtml code :
{code}
<rich:tree id="myTree"
var="node"
nodeType="#{node.type}"
toggleType="ajax"
selectionType="ajax">
<rich:treeModelRecursiveAdaptor roots="#{bean.roots}"
nodes="#{node.folders}">
<rich:treeNode title="#{node.path}"
type="folder"
onbeforetoggle="getSelectedPath('#{node.path}')"
ondblclick="chooseFolder('#{node.ecmId}', '#{node.path}')"
toggleListener="#{bean.treeToggleListener}">
<h:outputText value="#{node.label}" />
</rich:treeNode>
</rich:treeModelRecursiveAdaptor>
</rich:tree>
{code}
where getSelectedPath is a a4j:jsFunction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: