Hi Sven,
Am Freitag, 26. März 2010 schrieb Sven Meier:
> >the only difference in my proposal is to call removeAll earlier:
> >not in onBeforeRender of the next request cycle, but in onDetach of
> >the current request cycle.
>
> it makes a huge difference:
> If you call removeAll in onDetach, t
Hi Michael,
>the only difference in my proposal is to call removeAll earlier:
>not in onBeforeRender of the next request cycle, but in onDetach of
the current request cycle.
it makes a huge difference:
If you call removeAll in onDetach, the next request to a component
inside the ListView will
Hi Sven,
you wrote:
> there's no requirement for components inside ListView to be stateless -
> I wonder were you got that from.
I got that from the ListView class comment and from studying the code.
The comment says:
"By default, setReuseItems is false, which has the effect that ListView
repla
Hi Michael,
there's no requirement for components inside ListView to be stateless -
I wonder were you got that from.
You can have Links, Buttons or anything else in there so removing all on
detach is a recipe for disaster for the next incoming request.
Sven
Michael Gottschalk wrote:
Hi,
I
Hi,
I have a question concerning the serialization of subcomponents of ListView.
If I understand correctly, then the components that are added to a ListView in
the populateItem method should be stateless, since they are removed in the
onPopulate method each time the list view is rendered (as lo
lto:[EMAIL PROTECTED]
Sent: Sunday, September 21, 2008 10:09 PM
To: users@wicket.apache.org
Subject: ListView and Serialization
ListView and Serialization
First i like to say it was the framework that I was waiting for years.
Great job guys!
I did buy the wicket in action book which I did find ve
ListView and Serialization
First i like to say it was the framework that I was waiting for years.
Great job guys!
I did buy the wicket in action book which I did find very helpful but it
didn't help me solve this problem. I have problems with the ListView
and Serialization. I'm
