Hi!,
Following is my thought on ur question
ejbRemove() method should always be called under a transaction...
Now say u invoked remove() method on a bean which is in pool.
Container would do the following
. call ejbActivate() (in weblogic dirtyFlag is set to true; i.e beans state is dirty
and needs refresh)
. call ejbLoad() container always calls this callback method before start of a
transaction. Here the bean state would be refreshed with db.
. call ejbRemove()
So the instance variables would be refreshed before ejbRemove is called.
Just a question, why do we have to care if the bean is not in sync with the db when
removing it, its just the Primary key that we need .
I am not an expert, please let me know if u feel i am wrong or if u dont agree.
Thanx
Shiraz Zaidi
===========================================================================
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".
