Message-driven beans are stateless, server-side components that are used to
receive and process messages that Java clients send to them via JMS. They are
used to model processes and routers that operate on inbound enterprise
messages. Developers might use message-driven beans to integrate an EJB system
with a legacy system, or to enable business-to-business interactions. While a
message-driven bean consists of a bean class and an XML deployment descriptor,
it does not have a remote or home interface. Message-driven beans are not
distributed components, and do not have EJBObject and EJBHome references; they
respond only to asynchronous messages delivered from JMS.
In the future message-driven beans may be specified for other message systems
such as SMTP, but EJB 2.0 only supports JMS based message-driven beans.
Contrary to other comments on this list, MDB can receive also send JMS messages
using the JMS API, just like any other enterprise bean can send a JMS
messages. But they are driven, hence the name, by incoming JMS messages.
--
Richard Monson-Haefel
Author of Enterprise JavaBeans, 2nd Edition (O'Reilly 2000)
Co-Author of Java Message Service (O'Reilly 2000)
http://www.EjbNow.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
