Well, my thoughts for the discussion.
I think manipulating the state of a component with an ajax request is very common.
Think of the tree2 as an ajax component. Basicly it is a server side tree2 but the expand and collapse of the node would be triggered by a ajax request.
That would save much html traffic! But the state of the tree has to be kept in sync with every ajax request. There should be also a special rendering mode for the partial rendering of the child components and facets.

At the moment I can only use client side state saving because my application does support multiple windows. Therefor I use the x:saveState component for some beans.
I wonder if it is possible at all to keep the client state data in sync with the (partial) changed state on the server after a ajax request.

Reply via email to