Correct!. In fact we opted for Qpid taking lot of things into consideration leaving ActiveMQ behind.
Danushka On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle <p...@wso2.com> wrote: > Suho > > What is the use case for this? Users can already use ActiveMQ with the ESB > and other products via the JMS transport. There was (I think) a lot more > work involved in adding QPid as a broker including tying into the Identity > / User Manager as well as support for Multi-tenancy. > > Paul > > On 6 February 2012 07:04, Suhothayan Sriskandarajah <s...@wso2.com> wrote: > >> >> Currently Broker component only supports Qpid broker and it doesn't have >> the ability to send messages to other JMS brokers. >> This is because the provider url used to create the connection is >> programmatically build using the username, password, ip address, port and >> virtual machine name. >> >> Now I'm is the process of extending Broker's functionality to support >> ActiveMQ. >> In this process I can either programmatically build the provider url of >> the ActiveMQ or I can generalize the process by asking the user to add the >> provider url itself. >> In both cases users need to add the relevant broker jars (activemq or >> other ) to the libs. >> >> Here since we are shipping Qpid I thought it will be appropriate for the >> user to have two UIs, one Qpid specific and the other a general JMS UI >> which will ask for prover url and JNDI class name. >> >> Please give your ideas on this approach >> >> Thanks >> Suho >> >> >> -- >> *S. Suhothayan >> * >> Software Engineer >> *WSO2, Inc. *http://wso2.com >> lean.enterprise.middleware. >> >> *email: **s...@wso2.com* <s...@wso2.com>* cell: (+94) 779 756 757 >> blog: **http://suhothayan.blogspot.com/*<http://suhothayan.blogspot.com/> >> * >> twitter: **http://twitter.com/suhothayan* <http://twitter.com/suhothayan> >> * >> linked-in: **http://lk.linkedin.com/in/suhothayan* >> * >> * >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> 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 > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > 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 > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
