That's what I do as well. To me it seems that not using the model layer for logic is a legacy necessity from the time there was no JPA and EJB 3.
Question: Can we call this DDD, Domain Driven Design ? (Eric Evans) "Stephen Nelson" <[email protected]> wrote in message news:[email protected]... > On 9 Nov 2009, at 19:04, Dan King wrote: > > > Hi Dan > > I always try to keep as much domain/business logic in the domain > objects themselves. Otherwise you've [probably] gone through the pain > of O/R mapping for no tangible benefit. I generally use a service > layer for co-ordinating things e.g. calling a service; parsing a > result; storing a value in the data layer. It is then very easy to > wrap a transactional around it - and even easier if you're using > Spring. This kind of architecture is flexible without being overly so > and is clearly defined so you know where to go when bug fixing or > adding functionality. > > Regards, > -- > Stephen > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
