On 7/18/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Thanks for joining in. Btw, anyone who reads this is more than welcome > to participate. > > I don't think rendering just the component that receives the ajax call > suffices.
Right. I was thinking about more isolated components, like portlets. > We need to be able to regconize which components should be re-rendered, > and collect the render results, send that to the client, and interpret > that again to merge in our page. So the answer for rendering HTML back is "no". Components should report their "dirty" status, and should be easily addressed. Seems that Wicket already have component addressing using "component=..." part of GET request. The list of affected components can be returned either by a component that was acted on, or as a separate getDirtyList() call. Michael. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
