During a transaction you cannot remove a ssb also. We had this problem so we then decided to have a normal java class have the actual code and then from the bean we use to call that method. Same way another bean can also then access the Java class so you need not instantiate the ssb.
Anish -----Original Message----- From: Alex Paransky [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 1:13 PM To: [EMAIL PROTECTED] Subject: Question regarding removing of statefull session beans during a transaction... I have posted this question before, but really did not get any replies, so I decided to post it again. During a transaction, I create a statefull session bean, and use it. At the end of the method, I attempt to call remove on the statefull session bean, however, I get an exception stating that statefull session beans cannot be removed during a transaction. This IS what is in the spec. My question then, is how do I "cleanup" after creating a statefull session bean? I am using container managed transactions, so by the time the transaction ends, I don't have access to the local variable which was holding the statefull session bean. Could someone shed some light on this issue, please... Thanks. -AP_ =========================================================================== 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".
