I found slight difference between usage of <jee:jndi-lookup and definition of beans using JndiObjectFactoryBean.
Following configuration works well on local Jetty, but doesn’t work deployed on WebLogic server.
<jee:jndi-lookup id="connectionFactory" jndi-name="jms-cf"></jee:jndi-lookup>
<jee:jndi-lookup id="replyQueue" jndi-name="jms-queue0"></jee:jndi-lookup>
<jee:jndi-lookup id="requestQueue" jndi-name="jms-queue1"></jee:jndi-lookup>
But with this configuration, everything is fine.
<bean id="connectionFactory">
<property name="jndiName" value="jms-cf"></property>
</bean>
<bean id="replyQueue">
<property name="jndiName" value="jms-queue0"></property>
</bean>
<bean id="requestQueue">
<property name="jndiName" value="jms-queue1"></property>
</bean>
Little bit strange
Difference between jee:jndi-lookup and JndiObjectFactoryBean?
I found slight difference between usage of <jee:jndi-lookup and definition of beans using JndiObjectFactoryBean.
Following configuration works well on local Jetty, but doesn’t work deployed on WebLogic server.
But with this configuration, everything is fine.
Little bit strange