correction to statement there needs to be only a delete method on the dependent there is only a cascade-delete xml tag. sorry about that. Krishnan -----Original Message----- From: Reddy Krishnan [mailto:[EMAIL PROTECTED]] Sent: Friday, September 29, 2000 10:55 AM To: Orion-Interest Subject: RE: Cascade Delete( will orion support ejb-2_0 spec public Draft 2 ???) Hi In EJB 2.o spec draft 2. there are two new methods specified in the dependent objects delete() and cascadeDelete(). The deployment descriptor ejb-jar.xml also has a tag <cascade-delete/> under ejb-relationship-role. That solves this problem completely. Will orion support this spec soon? Thanks Krishnan -----Original Message----- From: Reddy Krishnan Sent: Wednesday, September 27, 2000 12:53 PM To: 'Orion-Interest' Subject: RE: Cascade Delete Hi, Regarding the same cascade delete problem. I have a clearFields() method which empties each of the collection holding relationships or dependent objects. If i call this from the client the objects gets deleted properly. But if i call this inside the ejbRemove() ( call clearFields() then call ejbStore()) this is not deleted in the database! Is it wrong to call such methods from ejbRemove? Thanks Krishnan -----Original Message----- From: Nick Newman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 27, 2000 9:13 AM To: Orion-Interest Subject: Re: Cascade Delete Hi, If you are using EJB 2.0 then (according to the draft specs) it is up to you to decide if dependent objects are deleted or not. However, if you are using EJB 1.1 and are storing a Collection of things in an Entity bean, then IMHO the container MUST delete the dependent objects along with the entity. I have reported this as bugzilla # 52. See that for further details. Nick At 04:53 PM 9/26/00 -0700, you wrote: >Hi, > >Having some problems while deleting a EJB. When i delete the ejb by >ejbobject.remove() method the dependent objects and relationship entries are >not >deleted from the database. Should this not be done automatically by the app >server. > >Is this a problem in Orion or is there some explicit delete that needs to be >done in the remove method implementation in the bean. > >Would appreciate any help on this. > >Thanks >Krishnan
