On 12 Nov 2009, at 10:33, KR wrote: > Hi Stephen, > > I do something similar as Dan and I keep the domain data and logic > together > in the model objects. > > My impression is that keeping data and logic apart is often just a > legacy > architecture that was introduced in the time before EJB3 and JPA > (but often > still used with EJB3 and JPA). Before EJB3 the persistency layer was > so > separate and limited that it was a technical requirement to do it > this way. > But that's no longer the case as JPA comes very close to making your > plain > old objects (POJO's) persistent. So this way of working is now much > closer > to regular object oriented design. > > This kind of design of course integrates the model and database > design. The > database schema becomes part of you're projects development. That > means that > this kind of architecture does not seem to work well with (static of > external) legacy database models that are not part of you're project. > > Regards, > Karen >
Hi Karen, I think we agree here - I'm advocating keeping the domain data and logic in the same class for the reasons you mentioned. I've only done a small amount of EJB3 in my past and I can attest to the lack of features it provided. Such that, entity beans were generally ignored in place of session beans and basically value objects containing data. So the present day technologies such as JPA are so much better - it's actually fun now! Cheers, -- 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 _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
