You can do: <table name="Some" baseClass="Parent" ...
So SomeClass/BaseSomeClass/SomeClassPeer/BaseSomeClassPeer will all still be generated, but BaseSomeClass will inherit Parent, which might allow you to do what you want. I say might as I'm pretty sure Parent will have to extend BaseObject as that's what BaseSomeClass extends by default (without baseClass=Parent specified). I think unless you do some hacking, the baseClass is only effective for classes that are also generated by Torque and hence already have BaseObject in their class hierarchy. If you really need complicated class hierarchies where the parent class is not Torque-generated (e.g. doesn't extend BaseObject), having your business objects delegate persistence sounds like a good alternative. - Stephen > -----Original Message----- > From: Marcellus A. Tryk [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 10, 2002 3:13 PM > To: [EMAIL PROTECTED] > Subject: Torque OR Mapping and Inheritance > > Hi all - > > So Torque generates 4 classes to map to a table, eg: BaseSomeClass, > BaseSomeClassPeer, SomeClass, SomeClassPeer. It's my understanding that, in > this case, I would augment SomeClass with business logic and so have a > useful class that supports persistence. But since SomeClass extends > BaseSomeClass, SomeClass can't extend any other class, which puts severe > limitations on my design. This seems like such an obvious problem that I > feel like I must be missing something. Am I misinterpreting the use of > SomeClass? Do I have my business objects delegate persitence operations to > corresponding persistence objects? Any explanation would be gratefully > received. > > Thank you, > > Mars > > -- > To unsubscribe, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
