Thanks for your repy manucet. If what you say is true (i'm convinced it is ;P) then that would be a major shortcomming of EJB2.0.
Luckily i already made a 'workaround' for the issue: i simply created an extra, autoincremented, primary key field and let the foreign keys just be the foreign keys. The down part of the solution is of course that there is now no database check on the uniqueness of the pair of foreign keys. O well... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916044#3916044 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916044 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
