On Thu, Jul 24, 2008 at 2:54 AM, Seref Arikan <[EMAIL PROTECTED]> wrote: > Let me just say that I do not feel comfortable about injecting business > logic related code into generated ORM classes. Even if the generated code is > OO (which is true in your product's case:) I am not comforable with adding > behavior for purposes other than persistence to that code. Since behaviour > can not exist on its own in an OO context, this implicitly forces me to > define domain objects as another set of classes. This leads to a situation > where I have two sets of classes that represent the same domain, but have > different responsibilities. One set covers business requirements, the other > covers persistence. I know that they can be combined, but It feels cleaner > this way.
Before partial classes, adding custom business logic to generated classes would have been out of the question, but have you considered their use in your scenario now that they are available ? Sébastien =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
