hi, I'm currently looking at ways to elegantly deal with a timeout of an SFSB. the only thing I can think of is to wrap the remote interface in some kind of proxy that knows how to recreate the bean if the reference becomes stale. I think this is the approach taken by rickard �berg's smart proxies. are there any other ways? is there a way to see that a timeout has caused an exception? I don't think so or am I missing something? the application I'm working on needs a SFSB because I need to pass some initialization info to the bean on creation (which differs with the client and therefore cannot be part of the bean environment). if it weren't for that I would use a SLSB as there is not a conversational state I need to maintain. as this client (a servlet) will be running for a long time I need to find a robust approach for handling timeouts. the reason I cannot pass that info with every method call is that the remote interface must be independent of that initialization info as there will be some stateless implementations in the future. thanks for any feedback, robert (-) Robert Kr�ger (-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH (-) Br�der-Knau�-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de =========================================================================== 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".
