Distributed Enterprise Messaging with MantaRay
Subject:   I don't quite get it
Date:   2004-12-14 01:47:32
From:   hasleh
I've read the article, and I've read a user manual on the MantaRay website. The user manual includes a description of how you can use MantaRay with JBoss, WebLogic and WebSphere. And it states that although you don't need it know, you might need to use JNDI to look up the QueConnectionFactory in the future. (It is highly recommended to use JNDI!)

What I don't understand is; I thought this was supposed to be JMS in a peer-to-peer kind of way? If I need JNDI, then won't I need an application server? (I'm sure there are standalone JNDI-solutions, but at least I will be tied to a server-application!) And if I have an application server, why would I want to use MantaRay instead of the JMS-solution provided with the application server?

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Amir Shevat photo I don't quite get it
    2004-12-14 04:25:08  Amir Shevat | O'Reilly Blogger [View]

    You can use MantaRay in two ways:

    1) As part of your POJO (plain old java objects) application, in this case you do not need a JNDI you just import and use the MantaRay JMS implementation. You can take a look at one of our examples in order to better understand how you can do it.

    2) Under J2EE application server, in this case the MantaRay will replace the MOM in the application server

    If you want to hook MantaRay to an application server - you will probably need a JNDI, because - when working with MDB's - they look for their connection factories and destinations in JNDI. You can't really get around it.

    As for why would you want to use MantaRay when you already have an application server - the question is the other way around - why use an application server if you got MantaRay ;-)-. When comparing MantaRay to other JMS providers (even those residing within an application server), you quickly come to the conclusion that MantaRay has better throughput AND there is no need for JNDI on the clients (the application server may need it for MDBs but the stand-alone clients don't need to do anything with JNDI). If you're going to use an application server - you have to go by its rules - if you want it to function in the way it is supposed to.