Hiranya There is no such thing as a "JMS broker". JMS is an API not a wire protocol. All brokers must have a wire protocol. ActiveMQ defines several of its own, Qpid uses a multi-vendor standard (AMQP).
I'm happy to keep the ActiveMQ ones in there commented out as well, but we need to make it easy to use our own Message Broker. Paul On 17 March 2011 08:29, Hiranya Jayathilaka <[email protected]> wrote: > > > On Thu, Mar 17, 2011 at 1:00 PM, Paul Fremantle <[email protected]> wrote: > >> I've been looking at using the MB with the ESB. >> >> There are a few things that jump out. >> >> 1) By default we ship the ESB with sample transport code for ActiveMQ. Can >> we change this to be Qpid related? >> > > We could. But Qpid is not really a JMS broker. It's an AMQP broker which > happens to support JMS. People might get the wrong idea if our default JMS > samples are all Qpid based. So instead how about having both ActiveMQ and > Qpid settings side by side? User can uncomment the one he prefers. > > Thanks, > Hiranya > > >> >> 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 >> >> 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? >> >> 4) If we could get that going, then it would be even nicer to show those >> queues/topics as URLs in the ESB config tooling (maybe via our discovery >> support?) but lets get the basics right first. >> >> Paul >> >> -- >> 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 >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- 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
