[EMAIL PROTECTED] wrote:
What I don’t understand is why the tree state is cached yet the model
is not, since it loads the new model properly. So… how can get it to
use a clean TreeState?
Thanks for any help on this.
Did you try a navigation rule for this? Bascally, upon navigation, the
internal state of components should be reseted. Another solution would
be to link your tree, using component binding, to a backing bean
property and acces the tree in that method. But i think a navigaiton
rule should be enough like it is for most components...
