Why are you creating a statefull session bean and then destroying it within the same transaction? At least to me that seems to raise the question of why are you using a statefull session bean? It would seem creating a regular Java object inside your method and store the state there would make more sense (and eliminate the problem as well).
Stateful session beans are really for keeping client state across method invocations, not inside of them. Cheers -----Original Message----- From: Alex Paransky To: [EMAIL PROTECTED] Sent: 10/4/01 1:12 PM 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".
