Guys, thread safety is to some point guaranteed, as long as you DON'T CREATE THREADS. So, if you don't use static nor create threads, then you have thread safety. This applies to both EJBs and dependant classes, and does not intersect the notion of a classloader.
Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of Bruce Powell > Sent: Sunday, November 24, 2002 7:57 AM > To: [EMAIL PROTECTED] > Subject: Re: Concurrent access to a method of a stateless > session bean. > > > The relevant classes could be in the ear itself & the ear > could have its own classloader, but I suspect you are right & > that is insufficient for thread safety. I thought the > container maintained a 'context' which associated a thread > with a bean, & kept code on the thread safe. bruce > > ============================================================== > ============= > 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".
