While I don't recommend it, you still could could, using something like this:
<object name="Engineer" decorator="com.foo.car.people.Engineer" /> where com.foo.car.people.Engineer extends com.foo.car.Person extends com.foo.car.BaseDecorator extends transfer.com.TransferDecorator. Then you could have Manufacturer, Quality, etc., all extend person with a separate decorator for each. ;) OR you could have Person which has a Role... 2 objects vs 30 or 40. Yeah, has-a over is-a any day. :D J On Nov 10, 2008, at 7:42 PM, Gavin Baumanis wrote: > > I was trying to over complicate things, I think, by trying to work out > how I was going to model via inheritance (and "ISA") the role to > person relationship. > Ie. I was going on the premise of the Engineer ISA user. > > Makes it that little bit simpler (for me in this case) when I realised > that a user "HASA" role. > > Thanks to everyone! > > Gavin. --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
