We are editing a tree structure(but can't use a tree as it is more complex and needed to be simplified for users). We have one page node.xhtml which shows it's children and each child can be edited. Naturally, we have a list of nodes stored in nodes in the conversation. When a user goes down one level, this nodes is replaced with the next guys children. Therein lies the problem. When our user clicks refresh, the previous list of nodes is no longer there and seam passes us in a new node to the edit function from the new list of nodes like the user clicked edit on this new list(which he didn't...he just clicked refresh).
How the heck do I work around this problem? I am sorta stumped here.