I have read it for more than few times but have no clue what exactly are you pointing on!? From that paragraph I cannot conclude that container should try to destroy relationships before trying to delete bean.
Finally, the question stays: how JBoss manages <cascade-delete/> deployment descriptor element (only <cascade-delete/> without <batch-cascade-delete/>)? BTW, in order to improve performance, is there something that I can define in JBoss to leave cascade delete functionality upon built-in cascade delete facility of the underlying DBMS? For example, BEA WebLogic does have proprietary element <db-cascade-delete/> telling the containter to leave cascade delete of related beanas (records) to DBMS. Is there something like this for JBoss? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845602#3845602 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845602 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
