Al Maw-2 wrote:
>
> Icy wrote:
>> *** What is the "best practise" to not instanciate "page aggregating
>> panels"
>> all the time? ***
>
> This isn't really a Wicket question.
>
> Your page is slow because doing database/remote operations is slow. It
> has nothing to do with creating Panels, but everything to do with the
> database access you're doing in the constructor of those Panels.
>
> You need to break those operations out into a service layer that can
> cache the results, then use that service layer in your constructor.
>
> Regards,
>
> Al
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
Dear Al,
Thanks for your help. If I interpret your answer correctly, this means that
the way my page is composed and the panels are instanciated is "the Wicket
way", I mean, correct.
Ok, what I could do then, is creating Spring managed singleton beans (I work
with a Wicket/Spring/Hibernate environment) - or at least one - that gather
the data for me, and let my panels request the data from the Spring bean. So
this somehow means I do the caching on my own, to fill the panels
efficiently, but if this is how it has to be done using Wicket, I will go
that way without thinking I am doing something unelegant.
Many thanks,
Icy
--
View this message in context:
http://www.nabble.com/How-to-instanciate-panels-best--tf4855189.html#a13895934
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
