Try simplifying your relationship config a bit by removing the jbosscmp-jdbc.xml config for your FantasyLineUp entity and just use the default relationship mapping that you get from ejb-jar.xml.
There used to be an issue with keys that were both PK and FK (as in this would not work) in JBoss 3.0 but I thought it had been fixed in 3.2 (or maybe its something completely different, staring all that XML hurts my eyes).
Anyway, as a general rule, when the stuff is not working, simplify your config back to defaults and once that works start adding additional config (in jbosscmp-jdbc.xml) bit by bit. Easier to debug!
Anyway, somethings wrong with the relationship config.
Through a process of trial and error, I've narrowed the problem down significantly.
First, I had to patch a template in Middlegen. This fixed several of my problems! However, now that that has been taken care of, I think that I've found a defect in 3.2RC3.
I have a table that contains 2 FKs both to the same column on a different table. When I remove one of the FKs, it deploys fine, but with both keys in place, I get:
Depends On Me: org.jboss.deployment.DeploymentException: CMP field for key not
found: field name=lineupId, ObjectName: jboss.j2ee:jndiName=com.ff.interfaces.FantasyTeamPlayerLocalHome,service=EJB
It might be worth a shot to try the 3.2 RC5 and see if the same problem still exists. Also should probably validate your descriptors against the DTDs if there are problems with the generator software you are using.
I'm not sure where that problem stems from, does your patched middlegen generate different content in the XML files now?
I just d/led RC4 and got the same exception. I'll put together a test case and submit it as a bug. Thanks for your help!