I assume it is Sculptor DomainObject we are talking about.
The reason is that we havn't found any need to generate the operations of the DomainObjects. Separation of generated and manually written code is done by a generated base class and manually written subclass. It is in the subclass you add methods to implement the behavior of the Domain Object. Domain Objects can have simple attributes and references to other Domain Objects. They can of course also contain behavior, otherwise it wouldn't be a rich domain model. However, the behavior logic is always written manually and not defined in the DSL. Practically, you just the methods you need to the DomainObject subclass (Java). No need to generate anything. wagnerma wrote: > > I have a starter question: > > In your metamodel the DomainObject has no operations. All > functionality/operations is modeled in the Service and Repository. From > our domain modeling standpoint, the DomainObject also has DomainObject > specific functionality, which is better modeled by the DomainObject. Now > the question: Why has your DomainObject no operation? > > Thanks for the answer, > > Marcel > -- View this message in context: http://www.nabble.com/Why-has-DomainObject-no-operation--tf3612070s17564.html#a10115010 Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
