Hi,
Correct me if I'm wrong but when one uses PageLink and passes in a Page
object (you have to construct it yourself) won't you end up with an
expensive cascade of Page construction? Meaning, Page1 links to Page2
links to Page3. When I construct a PageLink to Page2, its constructor
gets invoked, and in its constructor it links to Page3, so *its*
constructor gets invoked.
I remember a while ago we discussed why PageLink doesn't have a
constructor that takes in a PageParameters argument ... but in light of
this, don't we need one? I'm looking for a way for page construction to
always occur lazily.
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
