This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes JMS in Stateless Bean Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS in Stateless Bean" Watch "JMS in Stateless Bean" New topic

JMS in Stateless Bean

Viji San
Ranch Hand

Joined: Aug 12, 2010
Posts: 35
Usually, We use ServiceLocator Pattern to Cach lookup of JMS connectionfactory, Queue etc. In EJB3, we can use DI to inject the resource as below in session bean. My question is, how does container do this injection? Does container use something like caching the lookup? Do we need to really worry about it?

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 32818

Stateless beans are pooled so it wouldn't need to be repeatedly injected anyway, right?

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Viji San
Ranch Hand

Joined: Aug 12, 2010
Posts: 35
Right. But let's say if the pool size 50, then in that case, the container has to do at least 50 lookup when more beans are needed, right?
Don't get me started about those stupid light bulbs.
subject: JMS in Stateless Bean
It's not a secret anymore!