Hmm, I saw this in one commercial application using EJBs. There was an EJB, which inherited attributes from another Object (Extensible Object), which was a key value pair basically. I think something like this could be implemented into Torque easily. The Manager can take care about the saving of two tables (basically the main object and the extensible object with all the additional attributes).
Do you think, this is a good idea, or do you have any other suggestions? regards markus At 10:48 09.09.2002 -0500, you wrote: > > currently I am developing a small application using TDK2.2b3. I would >like > > to be able to extend objects with named attributes (e.g. the project >Object > > in my application has the attributes "name, start,...". Later a user >(or > > even myself) would like to extend the object with the attribute >"Project > > Manager". This could be done with a seperate table (extensible object) > > which holds the attribute name and the value and a link to the owner > > (OwnerId, OwnerName). > >Currently Torque only supports inheritance within a single table (e.g. >you'd have to modify the existing table and add the desired attributes >[ownerId, ownerName]). > >If you really want to do cross-table inheritance, OJB might be you could >look into. I haven't used it, but it's more mature in the inheritance >area than Torque is. > >- Stephen > > >-- >To unsubscribe, >e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> ---+++--------------------+++---------------------+++--- Markus M. May [EMAIL PROTECTED] Provide you with better J2EE support Please use my public key at: http://www.may-consult.com/mmay_mayconsult_com.key ---+++--------------------+++---------------------+++--- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
