Amila I think we should go ahead with what we have today. What I would really like is that there is a single Carbon JNDI (as for Data Sources). As we create queues and topics in the MB these are automatically registered, and the JMS transport should use the Carbon JNDI by default.
So if I create a queue called paul in the UI, then I should simply be able to reference jms:/paul in the transport and they will work together. Paul On 19 March 2011 04:31, Amila Suriarachchi <[email protected]> wrote: > > > On Wed, Mar 16, 2011 at 4:18 PM, Danushka Menikkumbura > <[email protected]>wrote: > >> Hi, >> >> The requirement is to install the Qpid (client) feature and configure JMS >> transport as usual to work with the MB. The issue here is that if you >> install it as a feature the libs get install into >> repository/components/plugin so that classes will not be visible to the >> CarbonContext. >> > > ESB build from the trunk, come with the Qpid component by default. > > I can configure an jms endpoint like this with that and it works. > > <endpoint> > <address > uri="jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.qpid.jndi.PropertiesFileInitialContextFactory&java.naming.provider.url=/home/amila/downloads/temp/server.properties&transport.jms.DestinationType=queue"/> > </endpoint> > > Is the requirement of this feature to have some real provider url which > dynamically loads all the queues instead of this file entry > > amp;java.naming.provider.url=/home/amila/downloads/temp/server.properties ? > > some think like this? > > <address > uri="jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=<carbonspecificInitialContextFactory>&java.naming.provider.url=<carbonserverproviderUrl>&transport.jms.DestinationType=queue"/> > </endpoint> > > thanks, > Amila. > > > > >> >> Senaka, do we have a fix for this?. It is not an issue anymore?. >> >> Thanks, >> Danushka >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
