This content has been marked as final.
Show 3 replies
-
1. Re: Why ActionSource2 not work in <rich:treeNode> component, in composite
mcmurdosound Dec 20, 2011 3:56 AM (in response to unders10d)I think the targets value is wrong:
targets="testForm:propertyEvent" because the tree and the treenodes itself will add own ids to the path from the form to the targeted commandLink.
Please use firebug or something similar to check the ID of the link(s).
-
2. Re: Why ActionSource2 not work in <rich:treeNode> component, in composite
unders10d Dec 20, 2011 6:08 AM (in response to mcmurdosound)Hi Christian, thanks for replay. I tried remove attribute targets from <composite:actionSource>, but nothing.
any else?
-
3. Re: Why ActionSource2 not work in <rich:treeNode> component, in composite
mcmurdosound Dec 20, 2011 6:47 AM (in response to unders10d)Hmmm no, my idea was to use the correct id-path to the commandLink since the tree will probably add its own id.
Like: "testForm:jid_123:propertyEvent"
You'll have to give the tree an id to prevent these generated ones (jid_123).