+1 agreed. Caching the data (models) coming from data providers and/or
services is the best approach
On 8/17/16 3:50 AM, Martin Grigorov wrote:
Hi,
I am not aware of such component.
Usually the caching is done in the service layer, not in the UI.
But if you prefer to do it with Wicket then do it in a Model that caches
the DB results.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Aug 16, 2016 at 6:03 PM, Marcel Barbosa Pinto <
[email protected]> wrote:
Hi,
I was just wondering if there is some component to instead of let the a
given component to render itself, check if there is a cache and display its
rendered markup, thus avoiding unnecessary rendering, this could be useful
for stateless components that need to display some list of categories from
the database etc.
Something like this:
class Header extends Panel{
add(new ExpensiveCategoryListView());
}
class Home extends Page{
add(new CachedComponent("headerContainer", Header.class))
}
The CachedComponent would first check if there is an already rendered
Header instance (could check in an in-memory store like, infinispan or
hezelcast)
What do you guys think?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
