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.



On Nov 11, 8:57 am, "Mark Mandel" <[EMAIL PROTECTED]> wrote:
> > I assume, now, that the object declaration (in the XML and the TO
> > creation too)  in this case is redundant, since I am only needing to
> > be able to manage the setting/getting of the issuetype id for each
> > ticket - which is created within the CAR object via the manytoone
> > relationship?
>
> > Gavin.
>
> If I read this right, I think you have got it worked out.
>
> You have your object, which is assigned a role... the role is really
> just a manytoone relationship.
>
> (You are actually using Composition over Inheritance, which is a good thing)
>
> Mark
>
>
>
> --
> E: [EMAIL PROTECTED]
> W:www.compoundtheory.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to