I have the same problem. I also don't have a primkey-field in the @ejb.bean tag, but that is because I have a composite key and a primary key class identified with @ejb.pk. "primkey-field" does not work with composite keys. The key fields themselves are tagged with @ejb.pk-field.
I don't know whether the problem has anything to do with the absense of "primkey-field", but it seems like a plausible theory. It ought to work, and I am pretty sure this is a bug in the SQL generation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838334#3838334 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838334 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
