Re: Cascade delete for CMP set mapping?

Cascade deletes aren't supported in Orion (yet), but I hear they should be soon. Hang tight :) -Pat - Original Message - From: Chris Turner To: Orion-Interest Sent: Tuesday, February 12, 2002 6:34 AM Subject: Cascade delete for CMP set mapping? Hi

RE: Cascade delete for CMP set mapping?

Chris, I believe that cascade delete is fixed in the next release. Regards, the elephantwalker www.elephantwalker.com -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris TurnerSent: Tuesday, February 12, 2002 6:34 AMTo:

RE: cascade-delete support

Title: RE: cascade-delete support as of 1.4.4 cascade delete is not implemented. I don't believe its in 1.4.5 either. Check changes.txt. So you have to put code into ejbRemove() to delete dependents of the object. -tim -Original Message- From: Christian Billen [mailto:[EMAIL

RE: Cascade Delete

but if my understanding is correct, the cmp beans move to the pooled state only AFTER ejbremove is called. -Original Message- From: Christian Eichinger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 03, 2000 1:35 AM To: Orion-Interest Subject: Re: Cascade Delete Hi, when looking

RE: Cascade Delete( will orion support ejb-2_0 spec public Draft 2 ???)

? 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

RE: Cascade Delete( will orion support ejb-2_0 spec public Draft 2 ???)

. 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

Re: Cascade Delete

Take a look at the ejb2.0-Specification(e.g. http://www.sdmagazine.com/uml/thinking/s0010to.shtml): Things like Dependent Objects have become a little bit clearer, and so it became clearer, what a cascading delete on the object-level means. greetings Stefan Frank - Original Message -

RE: Cascade Delete

-Mensaje original- De: Stefan Frank [SMTP:[EMAIL PROTECTED]] Enviado el: Miércoles, 27 de Septiembre de 2000 06:29 a.m. Para: Orion-Interest Asunto: Re: Cascade Delete Take a look at the ejb2.0-Specification(e.g. http://www.sdmagazine.com/uml/thinking/s0010to.shtml

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

RE: Cascade Delete

Hi Klaus, Thanks for the reply. As per EJB2 spec there is a createDependentObject abstract method for each dependent object but no deleteObject. In which case to remove the dependent objects we have to write some JDBC code and call it in BEans ejbRemove method. If i were to do that the

RE: Cascade Delete

() 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

RE: Cascade Delete

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