MDB: Difference between revisions
(→API) |
|||
| Line 11: | Line 11: | ||
=API= | =API= | ||
==Annotations== | |||
==Deployment Descriptors== | |||
==Code== | |||
==Example== | |||
A working MDB example is available here {{External|https://github.com/NovaOrdis/playground/tree/master/jee/ejb/mdb}} | A working MDB example is available here {{External|https://github.com/NovaOrdis/playground/tree/master/jee/ejb/mdb}} | ||
Revision as of 19:00, 17 March 2017
Internal
Overview
A Message-Driven Bean (MDB) is an asynchronous message consumer, invoked by the container as a result of the arrival of a message at the JMS destination serviced by the message-driven bean.
To a client, an MDB is a message consumer that implements some business logic running on the server. A client accesses an MDB by sending messages to the JMS destination associated with the MDB container of that type. MDBs are anonymous. They have no client-visible identity. MDB instances have no conversational state either, meaning they do not maintain state for a specific client. All bean instances are equivalent when they are not involved in servicing a client message. An MDB instance is created by the container to handle the processing of the messages for which the MDB is the consumer. Its lifetime is controlled by the container.
API
Annotations
Deployment Descriptors
Code
Example
A working MDB example is available here