what about (in addition to offering a remove-method in the api)
integrate component-tree lifecycle with JSR-299 Contexts (conversation
scope) - e.g. automatically clean up views when leaving a multi-page
wizzard?
Orchestra already does that by decorating the state-manager. However,
this worked only implementation specific, AFAIK. A cleanup of the API
of the state-manager and an API for accessing the view-states would
definitely be useful.
regards,
Martin