I'm having problems with a conversation scoped bean, where I am passing a page parameter and executing an action with said page parameter... The method seems to run twice.
For example I have a document tree that can expand and collapse, if I expand the top document it works fine, if I expand the second document it works fine, however if I collapse the former both documents are collapsed, which means seam is executing the action with the old document id, then passing the new document id in and running the action again.
Has anyone experienced the above? If so has anyone gotten around this?
My bad, it seems s:link was not holding the conversation properly.