The we need is not to have multiple request targets in a request
cycle, but to have one request target that handles the rendering of
multiple components. So instead of new ComponentTarget(component), you
would have something like new
MultipleComponentTarget().add(componentX).add(componentY).
We don't have that now, and it doesn't make sense to have one, as you
need some client specific seperation markup, like this piece of xml
here shows:
<components>
<component>
<input type="text" wicket:id="comp1" value="val" />
</component>
<component>
<input type="text" wicket:id="comp632" value="val" />
</component>
</components>
or, a very different approach:
<input type="text" wicket:id="comp1" value="val" />||||<input
type="text" wicket:id="comp632" value="val" />
where a sequence of |||| seperates components.
It thus depends on how the client wants to interpret things, and it
doesn't make sense to make a such a request target. Unless we make a
compound request target or something, but I don't think we will win
much opposed to creating a purpose specific request target when we
need it.
Eelco
On 1/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> I'm not yet too familiar with targets. If you could do
> addRequestTarget(new ComponentTarget(component)) from within an ajax
> handler, than it should be possible after a) moving the doRender()
> implementation to ComponentTarget and b) make some additional
> components methods public.
>
> 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
