Once you removed an entity bean it might still exist in the database,
but the EJB container should refuse to give it back to you, and if you
insist on using the reference you already got, through an exception.
Just file a bug report with BEA.
arkin
Michael Pikounis wrote:
>
> Hello all!
>
> I have the following problem when using the remove() method of a bean
> managed entity bean:
>
> step 1: call bean.remove() to remove the bean
> step 2: call Enumeration i = home.findBySomeCriterion( criteria )
>
> my enumeration contains the bean I removed, because (I think) weblogic does
> not call ejbRemove until the end of the transaction! Anyone knows of a way
> to force weblogic (4.5.1) to call ejbRemove immediately (when I call
> bean.remove()) rathen than wait until the end of the transaction?
>
> Alternatively, is there a way to tell weblogic to filter out "deleted" beans
> when it builds the enumeration from the finder method?
>
> Thanks,
> Michael Pikounis
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
