Why should it matter if the container tries to synchronize your bean with
the db before ejbRemove? The row/bean is going to get removed anyways...
Gene Chuang
Kiko.com
-----Original Message-----
From: Bogdan Ghidireac [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 5:06 AM
To: [EMAIL PROTECTED]
Subject: home.remove(pk) method problem
Hi,
I have a CMP EJB that contains some info and a serializable field. During
the development the object that is serialized into this field has been
changed (some variables have different names). My problem is that I cannot
use remove(primaryKey) method of the home interface because the container is
trying to synchronize the state of the ejb before performing the remove in
the database (see paragraph 9.4.3 from ejb1.1 specs). Is there a way to
force the removal of the entity bean without synchronizing its state ?
Regards,
Bogdan
===========================================================================
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".
