> - does it change anything if I passed listItem.getModel() ? Nesting model instances if fine imo. I do that a lot myself. This got better in Wicket 2.0, where we have typed models: IModel<League>, so that you can at least partially work strongly typed without needing to pass the actual objects.
> - if the former is also not a good idea how can I assure full > detachability (means no League object gets serialized to session)? The former is fine. But read this http://www.nabble.com/Sharing-parts-of-a-model-between-components...-tf2282995.html discussion for some talk about problems/ tradeoffs etc. (and if you have suggestions yourself, please share!) :) Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
