This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Is javax.naming.InitialContext ThreadSafe? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Is javax.naming.InitialContext ThreadSafe?" Watch "Is javax.naming.InitialContext ThreadSafe?" New topic
Author

Is javax.naming.InitialContext ThreadSafe?

Debopam Poddar
Ranch Hand

Joined: Jun 21, 2005
Posts: 49

Currently I am use following code to lookup EJB3 sateless session beans for normal POJO class. (We are in JEE5 so we can not inject Stateless Session Beans in normal POJO class I have to use look up)


So is Context object is ThredSafe? should I create Context object for each call [as shown in this code snippet] or I can reuse the Context for all threads?
 
 
subject: Is javax.naming.InitialContext ThreadSafe?
 
Similar Threads
JBoss and Head First EJB
Local Entity Bean not bound in EJB 2.1 on JBoss 4.2.3 server
Got problem when setup HelloEJB project in RAD
Clustering-test problem.
�Rich Client + EJB�