> > 1) By default we ship the ESB with sample transport code for ActiveMQ. Can > we change this to be Qpid related?
+1 > 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 > If we can have the JNDI configured under transport sender this should be possible, I am not sure we can do that w/o any code changes, though. > 3) At the moment I'm having to create the JNDI locally using the > FileProperties based JNDI. This is completely annoying. > > The real way this should work is that I should point my client JNDI at a > port on the MB server (preferably an HTTPS port) and then my client should > pick up all the information from that Registry based JNDI. And all the > queues / topics that are defined through the console should be automatically > defined in JNDI. > > Have we done anything like that? > We had a "local" Registry-based ICF initially but dropped it as we modified the UI to have permission definitions only. This should be part of the Qpid client feature. We can use Registry client to fetch JNDI details. Thanks, Danushka
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
