Craig McClanahan wrote:
Martin's approach does sound very feasible, but I have one question
(not having had time to look at the code yet) ... does the "component"
to which the request is routed belong to the component tree of the
view from which the asynchronous request was submitted, or is it
totally separate?
From what I could see it is a normal component within the component
tree. The way Martin has handled it is, that he basically uses the full
JSF infrastructure for the component but adds a phase listener and a
bunch of interfaces, which extend the component functionality with an
ajax lifecycle within the component.
So if you want to alter the component tree you definitely have to go
through the full refresh cycle at the current state of affairs.
