April 2003
Beginner to intermediate
380 pages
12h 25m
English
Content preview from Java Data Objects
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,
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
Message-driven beans are quite similar to stateless session beans. Both are stateless, and with each method call, the container establishes a transaction context based on the deployment-descriptor transaction attribute for the message-listener methods.
Message-driven beans implement the MessageDrivenBean interface for lifecycle callbacks and a message-listener
interface for business methods that is specific to the type of message
provider with which the bean is used. Message-driven beans used with the
JMS MessageListener interface have
only one business method, onMessage(
), that takes one parameter: an instance of javax.jms.Message. Those that are used with
another message provider must implement all of the methods of the
corresponding message-listener interface. The interaction with JDO is
the same in all cases.
The lifecycle of a message-driven bean (shown in Figure 17-3) is as simple as a
stateless session bean. To use JDO with message-driven beans, your
application uses the setMessageDrivenContext(
) method to save the context and look up and save the
PersistenceManagerFactory.
Figure 17-3. The lifecycle of a message-driven bean
To process the message-listener method, your application code
obtains a PersistenceManager from the
PersistenceManagerFactory and handles the message, performing JDO accesses as required. At the end of the business method, you close ...
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.