JMS in Stateless Bean

[Viji San]

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?

@Stateless
public class JMSMessageSender implements JMSMessageSenderLocal {

    @Resource(mappedName="jms/ConnectionFactory")
    private ConnectionFactory connectionFactory;

    @Resource(mappedName="jms/queue")
    private Queue queue;
    ...
	
	
	}

[Jeanne Boyarsky]

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

[Viji San]

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?