Juergen Donnerstag wrote:
Well, yes, I could add all those components to my Page, but that can be
few hundred Panels, and that sound like an overkill to construct.
Specially when probably only few of them will ever be rendered.
Not sure I understand your comment. Lets say you have a standard
wicket application with lets say 50 pages and each of these pages
contains a certain amount of Labels, Panels, Forms etc. You don't have
to add any extra Component to the Page to be able to re-render
components. It is all there already, except the URL which allows you
to invoke render(Component). Are we talking about something different?
Juergen
In the AJAX world there is not usually not 50 pages, there is usually
only one or sometimes few of them. It really sucks when I have to add
all the Components to the Page, even if only few of them will ever be
rendered (depending on the user actions). I'm using my AjaxWrapperPage
to be able to construct Components just-in-time, not when constructing
the (only) Page.
http://www.ajaxian.com/archives/2005/11/singlepage_vs_m.html
This whole thing works perfectly when I can force my AjaxWrapperPage to
go to a different PageMap.
--
Janne Hietamäki
Cemron Ltd
http://www.cemron.com/
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
