"/>
>
>
>
>
>
>Since OJB doesn't know about B, which declares the Person reference,
>you would need to use PersistentFieldIntrospectorImpl as
>PersistentField class in OJB.properties. You could also stick to
>PersistentFieldDirectAccessImpl, but then
a Driver.
Thanks for your help.
Later.
Mitch
-Original Message-
From: Gerhard Grosse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2003 3:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Inheritance mapping, storing new object associated with
pre-e xistingsuper object
Hi Mitch,
On Tue
rsistentFieldDirectAccessImpl, but then you have to explicitly map
class B and use inheritance mapping for User and Driver.
Cheers,
Gerhard
>
>Later.
>Mitch
>
>-Original Message-
>From: Gerhard Grosse [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, October 21, 2003 9:50 AM
Original Message-
From: Gerhard Grosse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2003 9:50 AM
To: [EMAIL PROTECTED]
Subject: Re: Inheritance mapping, storing new object associated with
pre-e xistingsuper object
On Tue, 21 Oct 2003 08:55:02 -0500, Mitch Norby
<[EMAIL PROTECTED]&g
On Tue, 21 Oct 2003 08:55:02 -0500, Mitch Norby
<[EMAIL PROTECTED]> wrote:
Hi Mitch,
How would you model this in Java? Wouldn't you just have two objects,
one of type User and another of type Driver, which happen to have
identical Person attributes? If you wanted to change a Person
attribute on y
We have the same issue. In our case, the classes are Person, User, and
Driver. All of these are concrete classes. However, this has nothing to do
with multiple inheritance. The subclasses do not inherit from multiple
superclasses. This is a case of non-exclusive subclassing.
As an example, a P
