Ok I got it. One question, consider that you have this model: Person 1xN Address
You have a screen that list a detailed view of a person, including a list of addresses. What approach do you use to implement it? - A service method that returns a Person entity with eager load of the list of Addresses? (if you don't need always the addresses this doesn't make sense) - A service method that returns a Person entity with lazy load of the list of Addresses? (it could be a problem in a JEE environment) - Two service methods, one to return the Person entity and another one to return the of addresses? Thanks, Eduardo S. Nunes On Tue, Mar 24, 2009 at 1:11 PM, Jeremy Thomerson <jer...@wickettraining.com> wrote: > Agree again. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Tue, Mar 24, 2009 at 11:11 AM, James Carman <jcar...@carmanconsulting.com >> wrote: > >> On Tue, Mar 24, 2009 at 12:08 PM, Eduardo Nunes <esnu...@gmail.com> wrote: >> > Yes, I understand you too. What do you do when you have to send a set >> > of entities and a calculation for each entity? you encapsulate it >> > inside another class? >> >> A domain-driven design advocate would say that the entity knows how to >> calculate what you need and you can ask it for the calculated value. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
