insert-after-ejb-post-create will not work if you use container generated primary keys (like autoincrement) because orimary key must be known before you set the relationship.
And youwill have problems during cascade deletes anyway because when the bean is about to be removed it will get cmr fields cleared first and if they are "NOT NULL" then you will have exception with foreign key violation... Frankly speaking the only solution I see so far is just not to use NOT NULL but do a check of CMR field against null in ejbCreate method and throw an exception if it is... If someone knows beter solution, please post here... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842398#3842398 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842398 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
