ejb lookups in spring config

[Billy Vandory]

Hi Folks, I'm trying to determine if the following is a good idea or bad idea: (This may be an EJB question)

In the ApplicationContext.xml :

First I get the JNDI properties for an EJB lookup

<bean id="jndiconfig" class="com.wakapeek.common.context.ConfigProperties">
<constructor-arg>
<value>/ejblookup.properties</value>
</constructor-arg>
</bean>

Then I pass those properties into the constructor of the InitialContext

<bean id="context" class="javax.naming.InitialContext" destroy-method="close">
<constructor-arg>
<ref bean="jndiconfig" />
</constructor-arg>
</bean>

Then I create the Stateless EJB

<bean id="categoryServiceBean" factory-bean="context" factory-method="lookup">
<constructor-arg>
<value>CategoryBeanRemote</value>
</constructor-arg>
</bean>

Then I inject the bean reference into a service object that will use the bean

<bean id="categoryManagerImpl" class="com.wakapeek.common.manager.impl.CategoryManagerImpl" scope="singleton">
<constructor-arg ref="categoryServiceBean"/>
</bean>


I was hoping this would cache the lookup and cache to the pool of stateless beans, instead of one particular instance of a stateless bean


Is the bean reference being cached or is a reference to the pool being cached? I want to make sure I am using the stateless bean pool provided by the app server.


Thanks alot,

Billy

[Mark Spritzler]

Or you could have the jee namespace used in your configuration and do

<jee:jndi-lookup id="myEjb" jndi-name="myJndiStringValueHere"/>

And Spring will do all the other work for you.

Mark