Alex Paransky wrote: > > The outer bean is not a SFSB, but a Stateless Session Bean, so I cannot > implement SessionSynchronization interface. > > You are right, if the outer bean WAS an SFSB, then I could have implemented > this interface to remove the inner bean at the end of the transaction, but > then the problem moves to the outer bean. Meaning, the outer bean cannot be > used in a transaction from a Stateless Session bean. > > So I am back to the starting point again....
Alex, It's not wise to try to use a SFSB as a second-level EJB. They are designed specifically for use by presentation layers running outside of the EJB environment. This has been discussed a number of times on the list - the usual reason mentioned being that SFSBs are "unreliable" in that their state may disappear without warning due to a server error or a timeout. You have just discovered another good reason why this architecture is unwise. Can I suggest that you refactor the functions of your application so that the outer EJB(s) are SFSB and that inner EJBs (if any) are SLSB or EB. You haven't said much about WHY you chose your current architecture, but it does need to be revisited and your packaging/distribution or whatever objectives achieved another way. cheers... Ian ======================================== Ian McCallion Alexis Systems Limited Romsey, UK Tel: +44 1794 514883 Fax: +44 1794 501692 ======================================== =========================================================================== 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".
