I have gotten a little farther: I have found that when I examine the two JDBCEntityMetaData classes, they both have correctly the "java:/jetsontestdls-ExternalDB" datasource name, but the JDBCRelationMetaData class persists in having "java:/DefaultDS" (since this is a 1:M relationship, so it isn't explicitly set), so when in JDBCStartCommand the datasource is called (line 135), naturally it fails (since there is no such datasource). The first question is "why is the JDBCRelationMetaData class set incorrectly?", but after that comes "why is the code executing this check for foreign-key relationships?" It goes through it just fine for relation-table relationships, since these have an explicitly set datasource, but my thought (uninformed) would be, why check this for foreign-key mappings, at least in this way? Why not simply check the other entity's datasource (easily reachable, albeit with a little object traversal) to find out whether or not the other table exists?
Does this description give anyone with more intimate knowledge of this code than I have any ideas? Thanks! David Sills View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831208#3831208 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831208 ------------------------------------------------------- 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
