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? So the FK's are really _not_ going to be PK's at all in the BusinessCard, hence the error message I am getting. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Harkness, David Sent: Friday, May 21, 2004 12:42 PM To: [EMAIL PROTECTED] Subject: RE: [Xdoclet-user] Relationship errors with WLS 8.1... [EMAIL PROTECTED] wrote: > OK, I did change everything to have fully qualified names, > and that eliminated one of the 2 issues I am having. Nice! Progress is good. :) > So, here is the second issue I am still having. > > On deployment, I get this error: > ================================= [java] Role > 'AutomaticPaymentAccount-belongs_to-BusinessCard' of > relationship 'BusinessCard-AutomaticPaymentBankAccount' > contains an invalid key-column value of > 'automaticPaymentAccountFK'. The key-column must specify a > primary key column in the related bean. However, there is no > primary key column named 'automaticPaymentAccountFK' defined > in the related bean 'BusinessCard' or else > 'automaticPaymentAccountFK' is not being recognized due to > case mismatch. > > /** > * This is a one (BusinessCard) to one (BankAccount) relationship. > * > * @weblogic.target-column-map > * foreign-key-column="bankAccountPK" > * key-column="automaticPaymentAccountFK" > **/ > public abstract com.wf.bd.ice.account.BankAccountLocal > getAutomaticPaymentAccount(); > public abstract void setAutomaticPaymentAccount( ... ); Unless target-column-map works differently than column-map, I'd bet your key-column tags are reversed. You should have * foreign-key-column="automaticPaymentAccountFK" * key-column="bankAccountPK" Having said that, given the error message it seems also that you are using the wrong keys. It is expecting the foreign key to be in the BankAccount bean: "The key-column must specify a primary key column in the related bean." So I think you need to reverse the attributes *and* switch the keys around (PK of related bean). 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 ------------------------------------------------------- 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
