On 1/15/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > ok so you render a single component's output using the target, but where > does it go? how does it get updated on the page? you still need javascript > to shove it into the right place on the page.
The component target still calls Component.doRender() (like we call Page.doRender() from the the page target). And like Page.doRender() it first gets the markup which than is rendered. It is the same concept. Yes, it does not solve of the AJAX problems. It does not render the body only, and the target does not allow to render multiple components. But as the junit test case proove, you could do it given the appropriate target. Ajax handlers which print the appropriate xml envelopes could call Component.doRender() to put the component response into the xml envelope. > > i was thinking of a situation where you need multiple components to be > updated from a single ajax request. like in an email client when you change > the folder you want the message list and the preview pane to be updated. so > one ajax event that leads to two components being updated on the page. see above Juergen ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
