Change Dinamically on Runtime the resourceReference/jndiName of a Queue/ConnFactory.

[Greater Than Equals]

You need to give the container a reference to a connection factory.

You should use a DefaultMessageListenerContainer (DMLC), not a SMLC.

Thank you...i think that i found another problem in this context:

<beans:bean id="outQueue"
class="org.springframework.jndi.JndiObjectFactoryBean" depends-on="PLUGCacheManager">
<beans:property name="jndiTemplate" ref="jndiTemplate" />
<beans:property name="jndiName" value="#{ PLUGCacheManager.queueReference }" />
<beans:property name="resourceRef" value="true" />
<beans:property name="lookupOnStartup" value="true" />
<beans:property name="proxyInterface" value="javax.jms.Destination" />
<!--<beans:property name="cache" value="false"/>
--></beans:bean>

I get the error MQJMS0003: Destinazione non corretta o non più valida; nested exception is javax.jms.InvalidDestinationException: MQJMS0003: Destinazione non corretta o non più valida

like i told before.

I try with javax.jms.Queue and expectedType com.ibm.mq.MQQueue but i get the same error.
Why if i set lookupOnStartup to true and i set the proxyInterface (or expectedType) too i get this error?

What is the problem in this case?

Really Thanks again.

IlPistolero

[Gary Russell]

I don't know, sorry; and I don't have access to a WAS/MQ environment to help you debug it.

[Greater Than Equals]

I don't know, sorry; and I don't have access to a WAS/MQ environment to help you debug it.

Hi gary no problem..i found a related issue to this problem...take a look, it's a bug opened since 2 years and 6 weeks..(since spring 3.0.3)...https://jira.springsource.org/browse...story-tabpanel