> That's was a really instructive post, thanks Eelco. > > In fact I'm actually struggling with this kind of issue. I've model > objects and then on my presentation layer the data are quite often a > bit different, and thus I wonder which way is the best. > > Igor had spoken about "form beans",
I think he meant the same thing (value objects). > However, you said you weren't a fan of this pattern, could you please > explain which approach you use ? I would really like it because I find > it really important for ease of development and maintainability. And > up to now I've found a way which fully pleases me. Tbh, I use it mixed, also because I'm not the only guy in the team (Igor and I actually work on the same project). My favorite way is to use the domain objects directly, but let updates (to the database) always go through services/ daos and *not* have transactions per request. I'll still use value objects every now and then because sometimes it's just easier to work with a 'flat' object that is focussed on a particular case. 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
