Although I think my question is purely one of object-oriented design, I should precede it by stating that my corporate development platform is. NET 2.0/VS 2005 and 3rd party/open source ORM frameworks are forbidden (don't ask).
My question has to do with how one goes about persisting business objects that are related either by association or dependency. Say, for instance, that class A contains instances of both class B and class C. When my DAL layer persists class A to my RDMBS, what idiom should I use to persist classes B and C. In other words, what layer and/or class should orchestrate the persistence of the nested objects without placing persistence aware code in class A? Furthermore, classes B and C form assoc ...
Go to the complete details ...