-
15. Re: rich tree and a4j support onselected - how to?
Tried for 1 hour and can't reproduse this behaviour. But I swear yesterday it was for 3 or 4 times: I redeployed, started the app and couldn't collapse nodes! Then changed switchType to ajax, redeployed again, started and everything worked! Strange... I'll write here if only I face it again.
-
16. Re: rich tree and a4j support onselected - how to?
Hi, Yurii!
The bug is reproducible sometimes upon two conditions: ajaxSubmitSelection attribute is set to "true" and a4j:support added for event "onselected". As you know the bug is not always reproducible so I don't have any ideas about its reasons yet...
All is OK when application send only one ajax request: if ajaxSubmitSelection is "false" or we remove a4j:support from tree. Tell me, please, if one of these conditions helps to solve problem. -
17. Re: rich tree and a4j support onselected - how to?
Good afternoon!
As I've mentioned in description of this bug on JIRA - yes, if I remove a4j:support from tree - everything works fine and there are no "twice" ajax requests.
And just tested right now about to switch ajaxSubmitSelection to false, leaving a4j:support - works well too. The bug is only reproducible(SOMETIMES - that's strange...) when both of these features are turned on(a4j:support and ajaxSubmitSelection).
Right now I use ajaxSubmitSelection=true with reRender of tree element. Everything works perfect. But the bug still exists, isn't it? Or it's not bug?
Thanks for answering, Sergey.