Yes; as travis said the AjaxDecodePhaseListener is a good example how myfaces handles the ajax stuff.
We are currently adding the ajax request the url value "affectedAjaxComponent+components_client_id" apart from the real value which we want to send to the server. During the ajax request the mentioned phase listener seeks the component through the "affectedAjaxComponent" value in the request parameter map. It can gain now a reference to the ajax component (and further to the corresponding renderer) through searching for the given client id and now every output can be rendered to client. Thats the way we are actually handling ajax requests; but sure thats not the one-and-only solution. regards, Gerald On 3/25/06, Travis Reeder <[EMAIL PROTECTED]> wrote: > Check out AjaxDecodePhaseListener in the sandbox and the ajax components in > the sandbox. There are some good examples in there. > > Travis > > > On 3/24/06, Hubert Rabago <[EMAIL PROTECTED]> wrote: > > On 3/24/06, Werner Punz < [EMAIL PROTECTED]> wrote: > > > You have to define the ajax call in the original renderer with a content > > > div or any other element content element, of the component and then > > > render the html in the ajax cycle, and > > > then on the html level replace the content holders inner html > > > part with the ajax rendered html. > > > That would be the trick on component level. > > > > I'm wondering, since you didn't have a period in this last sentence, > > if you'll allow me to complete it for you: > > > > > On page level it is quite different (I have to look into how the ajax > > > anywhere people were able to pull off ajax zones, given the fact that > > > JSF 1.1 does not allow partial rendering officially yet <insert>so I can > use that knowledge to write a custom panel that will allow ajax requests to > modify the server side component tree and update the controls shown on the > client.</insert>) > > > > Hubert > > > > -- Gerald Muellan Schelleingasse 2/11 1040 Vienna, Austria 0043 699 11772506 [EMAIL PROTECTED]
