> You probably do need to restore all of the ancestors of a component, > since things like NamingContainers had better be present.
I'm not so sure about the naming container aspect. If the components all used forceId you could store the component by client id. On the other hand for rendering purposes (take the ajax tree example) you probably would need the children so you can render the images, checkboxes, etc. that are inside of a tree node. > Also, not restoring the entire tree introduces extra problems - > especially if you want to respond to an AJAX request on one > component by refreshing others (a common > scenario over in ADF Faces). Hmm. I hadn't thought of that. I guess this might be a serious limitation. Do you think we could get away with updating only one component and handling the rest by updating the backing beans of the others? Another idea might be to only store the components for a particular view that are ajax enabled (and their children.) You could restore all of them automatically during the special lifcylce (Restore Partial View.) Just thinking of the top of my head here ... [snip] > -- Adam sean
