Then you can do the load lazy. Only when the link is clicked.
johan
On 3/22/06, Mats Norén <
[EMAIL PROTECTED]> wrote:
On 3/22/06, Eelco Hillenius < [EMAIL PROTECTED]> wrote:
> That's not the preferred way of working though. If you want to play
> nice with the framework, you should either make it a resource - imo
> the most elegant solution, and again, look at
> wicket-contrib-jasperreports - or a custom request target. By using
> WebResponse directly like that, you are circumventing the RequestCycle
> processing and it thus can be considered being a hack.
Ok, the resource way seems like a good strategy but it looks like you
pass the data in the constructor of the resource. That would mean that
the all the data is collected even if the link is never used, or am I
missing something?
I would like to fetch the data only if the link is clicked. I guess I
could do that by sending the DAO to my resource. Or making some kind
of DataSource interface and pass that to my Resource constructor.
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
