> It threw me for a loop when I saw that > nested components need to be added to their parent and not the page. > That is quite a different paradigm from what I am used to. =)
It's a commonly overlooked aspect in discussions about component oriented frameworks. Page is just another component, though it serves as the ultimate root component you use when you want to actually render your components to clients. But you can develop components with their own navigation means (e.g. using panel replacements), forms and other call backs etc, without ever thinking about the page it will be on. Wicket's concept of everything being nested components sometimes confuse people - especially when they come from using other frameworks - but it's ultimately what makes creating custom components with Wicket so easy, and what makes things like refactoring parts of the component tree without loosing behavior etc a breeze. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
