Hi,
you might consider to keep just the object model id in your button in
order to avoid capturing the entire object in your component.
On 28/08/2018 10:32, Tobias Gierke wrote:
I've accidently sent my follow-up mail directly to Sven, here it is
(and his reply) for the sake of completeness, just in case someone
else stumbles across this as well.
Cheers,
Tobias
Hi Tobias,
>As we're already using a LoadableDetachableModel for the repeater
itself, you probably meant I should override
ListView#getListItemModel() and return a LoadableDetachableModel
there, right ?
+1 exactly.
Sven
Am 28.08.2018 um 09:44 schrieb Tobias Gierke:
Hi Sven,
Thanks for your reply !
Hi,
your first solution was inefficient anyways, because every click
reloaded all Datas first, before acting on a single one only.
Inefficient in terms of database hits - yes. Inefficient in terms of
serialization cost/memory usage - no. As the table is fairly small
(way less than one million rows) and our application has a very low
number of concurrent users, I'm not too concerned with database query
performance.
You should use a detachable model instead, see JpaLoadableModel here
https://ci.apache.org/projects/wicket/guide/8.x/single.html#_detachable_models
As we're already using a LoadableDetachableModel for the repeater
itself, you probably meant I should override
ListView#getListItemModel() and return a LoadableDetachableModel
there, right ?
Cheers,
Tobi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
