« Return to Thread: JMS11Support in Mule2.0 not comaptible with that in Mule 1.4.x

Re: JMS11Support in Mule2.0 not comaptible with that in Mule 1.4.x

by ddossot :: Rate this Message:

Reply to Author | View in Thread

An option, but maybe not "the right option" (Andrew?), consists in sub-classing Jms11Support, override createDestination to perform the JNDI lookup and inject this custom support in your connector like this:

    <jms:connector name="yourJmsConnector" specification="1.1"
        connectionFactory-ref="yourConnectionFactory">
        <spring:property name="jmsSupport" ref="jndiJmsSupport" />
    </jms:connector>

    <spring:bean name="jndiJmsSupport" class="your.Jms11Support">
        <spring:constructor-arg ref="yourJmsConnector" />
    </spring:bean>

If you do not like sub-classing, you can just add a Spring interceptor on the createDestination method of the standard Jms11Support class (I have done this and can provide the config).

HTH
D.


On Fri, May 16, 2008 at 7:15 AM, muletester <hemadrim@...> wrote:

JMS11Support in Mule1.4 accepts jndiDestinations parameter and if this is set
to true, it does a look up of queue/topic in JNDI tree. How can we achieve
this similar functionality in Mule 2.0 in JMS11Support? If not, Is there any
other way where we can look up queue/topic in JNDI Tree, since current
version doesn't accept jndiDestinations or forceJndiDestinations.
--
View this message in context: http://www.nabble.com/JMS11Support-in-Mule2.0-not-comaptible-with-that-in-Mule-1.4.x-tp17275750p17275750.html
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



 « Return to Thread: JMS11Support in Mule2.0 not comaptible with that in Mule 1.4.x