Hi Kevin, Let me guess the answer to this one.
First we're talking about an ObjEntity, not a DataObject. So you'd never subclass it. As an example, one of my projects has WORK_ORDER, DISCONNECT_ORDER, CONNECT_ORDER (and so on) tables. WORK_ORDER is the common shared info by any kind of task. But you'd never have a WORK_ORDER entry without a subclass table. Thus, the template generator should never create WorkOrder as an abstract class. DisconnectOrder and ConnectOrder would inherit from that class and would not be abstract. On 5/30/07, Kevin Menard <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: Aristedes Maniatis [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 30, 2007 4:32 AM > To: dev@cayenne.apache.org > Subject: Re: Abstract Entities [Was: Modelling improvements: > inheritance + interfacing (Draft)] > > > * Changes to the code generation templates to generate > abstract java > > classes for such entities > > Yes and the setIsAbstract() and getIsAbstract() functions for > ObjEntity which go hand in hand. I'm clearly showing my ignorance on the matter here, but what does it mean for an object to know that it's abstract? Isn't that a property of the class? What happens when you subclass the ObjEntity? -- Kevin
