You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Bert <ta...@gmail.com> on 2009/03/03 08:13:08 UTC
Repeater that disposses content after rendering?
Hi,
perhaps this does not make sense, but is there a Component that
discards all child components after the rendering, before
the serialization?
Would this make sense for components that render a large amount
of child's (tables with many cells) where all of them could be
reconstructed from a LDM in the repeater? Would this save space
in the page store / session?
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Repeater that disposses content after rendering?
Posted by Igor Vaynberg <ig...@gmail.com>.
refreshing view clears its content before render, not after render. if
you have a link in your table cell, or any component that requires a
callback and you clear the items after render than the link wont work
because when it is clicked the component that is supposed to receive
it is no longer there.
if this is not a concern for your particular usecase you can roll your
own repeater quiet easily using a subclassed refreshing view or
something similar.
-igor
On Tue, Mar 3, 2009 at 12:54 AM, Bert <ta...@gmail.com> wrote:
> That was my first idea and i checked the javadoc and source (without
> following too deep
> into the stack (DefaultItemReuseStrategy is where this is done?).
>
> Good to know that the RefreshingView is behaving like this, i use it
> rather often.
>
> Thanks for the reply,
> Bert
>
> On Tue, Mar 3, 2009 at 09:43, Martijn Dashorst
> <ma...@gmail.com> wrote:
>> RefreshingView?
>>
>> Martijn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Repeater that disposses content after rendering?
Posted by Bert <ta...@gmail.com>.
That was my first idea and i checked the javadoc and source (without
following too deep
into the stack (DefaultItemReuseStrategy is where this is done?).
Good to know that the RefreshingView is behaving like this, i use it
rather often.
Thanks for the reply,
Bert
On Tue, Mar 3, 2009 at 09:43, Martijn Dashorst
<ma...@gmail.com> wrote:
> RefreshingView?
>
> Martijn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Repeater that disposses content after rendering?
Posted by Martijn Dashorst <ma...@gmail.com>.
RefreshingView?
Martijn
On Tue, Mar 3, 2009 at 8:13 AM, Bert <ta...@gmail.com> wrote:
> Hi,
>
> perhaps this does not make sense, but is there a Component that
> discards all child components after the rendering, before
> the serialization?
>
> Would this make sense for components that render a large amount
> of child's (tables with many cells) where all of them could be
> reconstructed from a LDM in the repeater? Would this save space
> in the page store / session?
>
> Thanks in advance.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org