Johan Compagner wrote:
I think having one page to do everything will not work quite right in
wicket. Because what is the start markup then?
Everything?? Where does all the markup come from?
Or do you just have 1 page but 50 panels?
What you can do in youre 1.2 in youre situations is just use a panel
(not a page) as a wrapper around youre component
I still don't get it where that component does get its markup from. It
can't be from the page its markup. So is that component
always a panel with its own markup? (then you can render it stand alone)
johan
Well currently I have few Pages and tons of Panels, and everything works
great. The only problem was one of these few Pages gets expired because
of my WrapperPage. And yes, my components are always Panels with their
own markups.
I don't want to attach all my components to the Page if they're not
really needed later, because that would cause the page state to grow too
much.. And there are already PageMaps to handle throwing away old stuff.
Sure, if I can render a non-attached Panel, that solves most problems.
--
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
