> With regard to the Login/Welcome example, I have a problem with the > Login's page's mutator methods being called in the onClick() in the > Welcome page. Your scenario requires that Welcome know too much about > Login. If Welcome and Login depend on the same model, and Welcome > changes the model, then when control is passed back to Login it should > be able to act on that change without the need for Welcome to know about > it. I don't see yet where Login has the opportunity to act on the model > change before the page is displayed. Again, is this where > onBeforeRender() comes in? Or some other method?
I don't really get what you're after tbh. You can make your components to be completely independent. In the end, they need to function in a page/ component hierarchy, but this doesn't have to be related to how components work with their models. The onAttach/ onBeforeRender methods can be used if you need to do special preparation before the rendering starts, but if I understand you correctly, this wouldn't be the best way to go. What you do when constructing the page is set the initial component hierarchy, and that hierarchy can change later on, typically through callbacks like link clicks and form posts. Take a good look at the wicket-examples project for inspriration, and if you have concrete cases you struggle with, please explain in more detail. Eelco Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
