Hi Michael,
why dont u do tx.commit() and then call the find method --- that should
solve the problem. And in 5.1 WLS I tried to access the bean twice in the
same tx and it gave an error -- this is because while in tx the entity bean
is locked and is not free until the tx ends.
U can also try setting delay-updates-until-end-of-tx to false and see if
that works.
HTH
Ana
-----Original Message-----
From: Michael Pikounis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 14, 2000 6:48 AM
To: [EMAIL PROTECTED]
Subject: ejbRemove immediate?
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".
