May 2009
Intermediate to advanced
330 pages
10h 34m
English
Content preview from Java Message Service, 2nd EditionBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Message-Driven Beans
Although session beans and web components can act as JMS
producers, these components can only consume JMS messages
synchronously using one of the MessageConsumer.receive() methods. Calling the
receive() methods causes the JMS
client to block on the currently running thread and wait for a
message.[12] These methods are used to consume messages synchronously,
whereas MessageListener objects are
used to consume messages asynchronously.
Only the message-driven bean and application client components can both produce and consume asynchronous messages. The web and session components cannot act as asynchronous JMS consumers because they are driven by synchronous request/reply protocols, not asynchronous messages. Web components respond to HTTP requests while session beans respond to Java RMI-IIOP requests.
The fact that neither web components nor session beans can asynchronously consume JMS messages was one of the things that originally led to development of the message-driven bean. The MDB provides Java EE developers with a server-side JMS consumer that can consume asynchronous messages, something that wasn’t supported in the early versions of Java EE.
While most JMS vendors provide the message-brokering facilities for routing messages from producers to consumers, the responsibility for implementing JMS clients is left to the application developer. In many cases, the JMS clients that consume and process messages need a lot of infrastructure in order to be robust, secure, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.