snippysnippy > > So it's *exactly* like the airline sample, then. Did you look at that?
Yes, it probably is very much like the airline example. I've discussed this with Eivind today, and we figured out it would probably be a good idea to try to deploy the airline app to weblogic, and see if the problem reincarnates there. Placed on personal TODO list, though. > >> Result is that entity bean for B gets FK/PK fields acting both as CMR and CMP fields. Rules are approx. as follows: 1) a CMR field is snip snip snip> > Create A and C first and then create B ;-) > -or ask on http://newsgroups.bea.com/ This is actually what is done, and it has been verified that A and C both are assigned valid id's from autogenerator, so the problem is that the ids (PK's) are never transferred to the PK fields of the PK class of bean C, probably due to the CMR/CMP confusion. However, I got around the problem by giving the B table its own autonumber PK, though conceptually not neccessary. As a consequence, my ORM model is somewhat messed up. I can live with that for now, though. Regards, Kristoffer Moe Senior Consultant Elan It ReSource ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ middlegen-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/middlegen-user
