Chapter11 中间件 J2EE JMS.pptVIP

Sequence of Events Asynchronous Receive Receiver Code: Asynchronous Receive Message-Driven Bean (MDB) JMS Within the J2EE Platform Enables J2EE components to send and receive asynchronous messages: Adds benefits of messaging to J2EE Adds benefits of J2EE framework to JMS EJB 2.0 Final Draft Standard establishes a new kind of bean: Message-Driven Bean (MDB) Message Bean implements MessageDrivenBean interface implements javax.jms.MessageListenener interface ——Is JMS Consumer Message Bean implements MessageDrivenBean interface implements javax.jms.MessageListenener interface ——Is JMS Consumer Configured as listener for queue/topic No home or remote interface onMessage method contains business logic Activated upon message arrival Asynchronous Stateless Unlike other EJBs: MDBs have no Home/Remote Interfaces MDBs only indirectly interact with clients MDBs cannot be created/removed by client actions MDBs are managed solely by the container MDBs process messages asynchronously MDBs support concurrent processing of Topics Queues(in JMS this would have to be specially coded by the developer) Note: one MDB can only interact with one Queue / Topic Message-Driven Bean Instance Executes on receipt of a JMS message Shares the following characteristics of stateless session bean Can be transaction-aware May update shared data in an underlying database Is stateless and relatively short-lived Notable difference : No home or remote interface Lifecycle MessageDriven Bean Instance Adding Instance of Message-Driven Bean to a Method-ready Pool MDB Example: MDB Example: Deployment Descriptor JMS Problems Issues Developer typically calls JMS from a stateless session bean No support for component development Developer must create a MessageListener class, whose instances come from a server-wide session pool Topic/queue classes tightly tied to available server resources No container management for scalability, transactions, etc Developer must develop queue/topic pooling classes “Start-up”