I worked out the problem, and will in fact submit a bug report, as this is a pretty big one. It's a problem with the code that reads the jbosscmp-jdbc.xml.
This problem seems to occur when there is no datasource set up that corresponds to the default datasource in standardjbosscmp-jdbc.xml, and you try to deploy a foreign-key relationship. The workaround is to create a bogus datasource that does correspond to standardjbosscmp-jdbc.xml. (You may get unexpected results if create tables is set to true, of course, but since this is a bogus database, who cares?) The fix would be to read the datasource for a foreign-key relationship from one of the entities involved, which is not done now. I have a solution that seems to work, and will submit that as well. David Sills View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831415#3831415 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831415 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
