On Thu, Mar 17, 2011 at 1:45 PM, Hiranya Jayathilaka <[email protected]>wrote:
> > > On Thu, Mar 17, 2011 at 1:15 PM, Rajika Kumarasiri <[email protected]>wrote: > >> >> >> On Thu, Mar 17, 2011 at 1:00 PM, Paul Fremantle <[email protected]> wrote: >> >>> I've been looking at using the MB with the ESB. >>> >>> There are a few things that jump out. >>> >>> 1) By default we ship the ESB with sample transport code for ActiveMQ. >>> Can we change this to be Qpid related? >>> >> >> I think we should maintain both ActiveMQ and a Qpid/MB sample. Lot of >> people are using ActiveMQ in their PoCs and there should be a sample which >> works out of the box. >> >> >>> >>> 2) By default the Axis2 JMS transport requires the JNDI information in >>> the URL >>> >>> (e.g.) >>> jms:/weblogic.examples.jms.exampleQueue?transport.jms.ConnectionFactoryJNDIName=weblogic.examples.jms.QueueConnectionFactory&java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory&java.naming.provider.url=t3://localhost:7001&transport.jms.DestinationType=queue >>> >>> Is there a way we can specify default JNDI configs for the ESB JMS >>> transport sender? So this way we would only specify the JNDI name of the >>> queue itself? e.g. jms://paulsQueue >>> >> >> No. Transportsender picks the JNDI informations from the transport URL. >> > > No Rajika. JMS transport already supports this. Currently there's a bug in > the transport which prevents this function from working properly. But I > submitted a patch for that a few weeks ago. With that you can specify your > EPR like "jms:/Foo?transport.jms.ConnectionFactory=default" where "Foo" is > the queue name and "default" is the connection factory name defined in the > axis2.xml which contains the JNDI settings. > Yes, I just looked at the source. Thanks for the correction. Rajika
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
