| Re: [eclipselink-users] Basic Design Question |
I would say yes, that is the point of having an object model. But there are many different design patterns and philosophies, so this is just an opinion. If you also define validation rules in the UI or the database, then there can be some redundancy, so you may choose just one place that works best for your application. RogerV wrote: > > Does business logic have any place in an entity definition? - for example > validation or should this always be done at a "higher" level? > > Regards > ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http://wiki.oracle.com/page/TopLink TopLink Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , http://www.nabble.com/EclipseLink-f26430.html EclipseLink Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence -- View this message in context: http://www.nabble.com/Basic-Design-Question-tp25800771p25803242.html Sent from the EclipseLink - Users mailing list archive at Nabble.com.