[EMAIL PROTECTED] wrote:
> Here is 1 issue with that though.
> I have this:
>
>
> BusinessCard
> =============
> productPK
> automaticPaymentAccountFK -> BankAccount.bankAccountPK
> electronicPaymentAccountFK -> BankAccount.bankAccountPK
> overdraftProtectionAccountFK -> BankAccount.bankAccountPK
>
> and
>
> BankAccount
> ============
> bankAccountPK
>
>
> So, each of the foreign keys in the BusinessCard are pointing
> to a row in the BankAccount Table. That is the relationship.
>
> Does that make sense?
Okay, as I understand it, then, you have *3* independent uni-directional
1:1 relationships from BusinessCard to BankAccount. BusinessCards
related to a BankAccount will not be visible from the BankAccount
itself, correct? That's the uni-directional part.
> So the FK's are really _not_ going to be PK's at all in the
> BusinessCard, hence the error message I am getting.
The FKs are in the BusinessCard bean, and they should reference the
BankAccount's PK. Comparing it to my beans (I don't have any 1:1, but I
have a few uni-N:1 [children see parent] that work this way), I think
you need to specify the key columns like this:
@weblogic.column-map
key-column="bankAccountPK"
foreign-key-column="automaticPaymentAccountFK"
The other two should look exactly the same except you'll specify a
different foreign-key-column (electronicPaymentAccountFK and
overdraftProtectionAccountFK). Give that a shot and let us know.
David Harkness
Sr. Software Engineer
Sony Pictures Digital Networks
(310) 482-4756
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id66&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
