[EMAIL PROTECTED] wrote:
> I tried that, and here is the deployment error I get (even
> though it is not true. Those columns exist):
Oops, I think I reversed the wrong pair. Since the source bean is
Guarantor, the "column-map" tags should be for guarantorPK while the
target tags should be for bankAccountPK. I got it backwards because I
usually put the PK on top and the FK on the bottom -- just didn't read
closely enough. Try this (swap the key-column tags):
* @ejb.relation
* name="Guarantor-BankAccount"
* role-name="Guarantor-has-BankAccounts"
* target-ejb="BankAccount"
* target-role-name="BankAccount-has-Guarantors"
* target-multiple="yes"
*
* @weblogic.column-map
* key-column="guarantorPK"
* foreign-key-column="guarantorPK"
*
* @weblogic.target-column-map
* key-column="bankAccountPK"
* foreign-key-column="bankAccountPK"
The error you got makes sense because it was looking in the BankAccount
table for guarantorPK. Of course, I don't see how this could be related
to the problem with the CreditApplication bean, but at least this
relation will be working. :)
I have another question about the 3 1:1 relations: Where are the foreign
keys? Are there 3 FKs in the CreditApplication table or 1 FK in each of
the related tables?
David Harkness
Sr. Software Engineer
Sony Pictures Digital Networks
(310) 482-4756
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
