Hi together, I'm trying to get an EJB component running with jboss-3.0.1RC1 and am experiencing the following problems with the CMP 2.0 engine:
I have 12 tables with many 1:n relationships and would like to have the database check referential integrity. So I added foreign key constraints and not null check constraints to the schema. Unfortunately, it seems that JBoss is inserting the colums already between ejbCreate and ejbPostCreate so the foreign key fields are not set and the database throws an exception as it should. After accepting not to have these consistency checks in place for now, I think I found a similar issue in conjunction with <cascade-delete/>: When removing an '1'-bean, instead of directly deleting the relating instances of the 'n' bean, it seems that at first only the relation pointer is nulled. I confirmed that by putting debug code into the ejbStore() method. Perhaps because of concurrency effects and using a different access path (the scenario is 1:n:1), I sometimes also encounter a bean instance where the relationship getter returns null. Are these known issues in the 3.0.1RC1 release? If so, is there a tagged version in cvs that fixed them? Thanks, Olaf BTW: What cvs tag corresponds to the build distributed as jboss-3.0.1RC1.zip? I don't want to download 20 MB all the time so I tried some tags, but when debugging, the editor always jumps after the last line. :-) ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
