> Also, reloading the entity from "state zero" every time could be > problematic when incrementally updating it using ajax.
Not if you save it every time :) But yes, if you do an update in steps, and only want to commit changes at the end (relevant not only with Ajax, but also e.g. with a wizard) this clearly wouldn't be the way to go. Working on a detached object or even value objects would be better then. I think you can mix approaches without problems if you are just aware of what you're doing. Sounds like a good item for the WIKI btw. 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
