Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 68536 invoked from network); 12 Jul 2006 15:32:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jul 2006 15:32:08 -0000 Received: (qmail 95543 invoked by uid 500); 12 Jul 2006 15:32:05 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 95456 invoked by uid 500); 12 Jul 2006 15:32:04 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 95445 invoked by uid 99); 12 Jul 2006 15:32:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2006 08:32:04 -0700 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [68.142.206.242] (HELO smtp109.plus.mail.mud.yahoo.com) (68.142.206.242) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 12 Jul 2006 08:32:03 -0700 Received: (qmail 72588 invoked from network); 12 Jul 2006 15:31:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:In-Reply-To:References:Mime-Version:X-Priority:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=jDmALMlMfKTWMPJVIpxQ6kAtcTIYrLsRj2qxXzItYpleEED6/argrex3sQYIn3uv1PmHLd2JfNCXGTj/EwqssMtbPz6BBOclQFzq03nWEnaYlEBDmfU8I5sDs7dDX+hYEA5jS7PZ4xjaDCp86vCph9cT6LeNGGNFSS4jkkEdRBw= ; Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with plain) by smtp109.plus.mail.mud.yahoo.com with SMTP; 12 Jul 2006 15:31:41 -0000 In-Reply-To: <84581975727889@lycos-europe.com> References: <84581975727889@lycos-europe.com> Mime-Version: 1.0 (Apple Message framework v749.3) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <13E14178-129C-42CE-A8E5-A35BEADD795B@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: Entity bean can not remove itself Date: Wed, 12 Jul 2006 08:33:06 -0700 To: user@geronimo.apache.org X-Mailer: Apple Mail (2.749.3) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I haven't studied the specs on this yet. Sun's example clearly shows the entity bean calling ejbRemove() from a business method in the entity bean itself. I would definitely expect this to have undefined behavior since it is a lifecycle method intended to be called from remove on one of the interfaces. However, I haven't looked for a definitive statement in the spec yet, and I suspect there isn't one. I would expect that calling remove on the appropriate interface, after marking the entity bean reentrant, should work. It's not clear to me if you have tried this yet, could you clarify? In any case crashing the server as a result of calling ejbRemove() directly seems to me to be a bug. Could you file a jira for this with as many details as possible? many thanks, david jencks On Jul 12, 2006, at 5:35 AM, mahu2425 wrote: > Hello Dain, > > I couldn't find it in the specs either, but I think it makes sense, > that an entity bean can remove itself. > > An example, that an entity bean can remove itself is also given at > Sun's J2EE tutorial: > http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMSJ2EEex3.html > > > I my opinion this feature should be added in the next version of > Geronimo. I also found a few posts in the internet, that this > problem occured on several other J2EE server and has been fixed there. > > > Best regards, > > Markus > > Benachrichtigung bei E-Mail Empfang! - http://mail.lycos.de/app/ > lycosinside/setupLI.exe