Re: [Carbon-dev] Getting the JMS transport to work with MB(Qpid) inside Carbon

Fri, 18 Mar 2011 21:31:38 -0700 

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&amp;java.naming.factory.initial=org.apache.qpid.jndi.PropertiesFileInitialContextFactory&amp;java.naming.provider.url=/home/amila/downloads/temp/server.properties&amp;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&amp;java.naming.factory.initial=<carbonspecificInitialContextFactory>&amp;java.naming.provider.url=<carbonserverproviderUrl>&amp;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

Reply via email to