|
»
« 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 Travis Carlson-2
::
Rate this Message:
Mule 2.0 no longer handles JNDI lookups, the idea being that you use
Spring's <jee:jndi-lookup> for that and inject the resulting bean into
your Mule config:
http://static.springframework.org/spring/docs/2.0.x/reference/xsd-config.html
However, in the case of JMS Destinations, there's nowhere you can inject
that in the config, so I'm afraid you'll have to go with David's
workaround for now and we'll create a JIRA to expose that in the config
somehow.
Thanks,
Travis
On Fri, 2008-05-16 at 15:23 -0700, muletester wrote:
> Thx for your response dssotot.
> The problem with first option is your subclass of Jms11Support needs to know
> about the jndi environ properties like initalcontext, provider url etc,. and
> Jms11Support doesn't define any of these. So the subclass should define
> these and accept them either in a constructor or via setters, to do a
> lookup. Correct me if I'm wrong on this.
>
> Can you please provide your spring interceptor config?
>
>
>
> ddossot wrote:
> >
> > 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
> >>
> >>
> >>
> >
> >
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Spring's <jee:jndi-lookup> for that and inject the resulting bean into
your Mule config:
http://static.springframework.org/spring/docs/2.0.x/reference/xsd-config.html
However, in the case of JMS Destinations, there's nowhere you can inject
that in the config, so I'm afraid you'll have to go with David's
workaround for now and we'll create a JIRA to expose that in the config
somehow.
Thanks,
Travis
On Fri, 2008-05-16 at 15:23 -0700, muletester wrote:
> Thx for your response dssotot.
> The problem with first option is your subclass of Jms11Support needs to know
> about the jndi environ properties like initalcontext, provider url etc,. and
> Jms11Support doesn't define any of these. So the subclass should define
> these and accept them either in a constructor or via setters, to do a
> lookup. Correct me if I'm wrong on this.
>
> Can you please provide your spring interceptor config?
>
>
>
> ddossot wrote:
> >
> > 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
> >>
> >>
> >>
> >
> >
>
---------------------------------------------------------------------
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
| Free embeddable forum powered by Nabble | Forum Help |
