This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes JMS: looking up queues ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS: looking up queues ?" Watch "JMS: looking up queues ?" New topic
Author

JMS: looking up queues ?

Sol Mayer-Orn
Ranch Hand

Joined: Nov 13, 2002
Posts: 311
I'm new to JMS, and would appreciate it if someone could please clear up this confusion...

There appear to be 2 ways to access a Queue object:



I've managed to get it working both ways.
And I see one obvious advantage of Method 2 (queues & managers are configured through the container admin, and not inside the code).

But apart from that, are there any other important differences ? would it affect my application design or performaces ?
In particular, suppose we put aside the initialization times ( assume "ctx.looup" or "session.createQueue" are called once on application startup). Will there be a difference in performance - will it take longer to send/receive JMS messages ?

Thanks very much !
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: JMS: looking up queues ?
 
It's not a secret anymore!