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: **[email protected]* <[email protected]>* 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
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to