Java Message Service Each MOM vendor implements its (Tomcat hosting)
Saturday, September 15th, 2007Java Message Service Each MOM vendor implements its own networking protocols, routing, and administration facilities, but the basic semantics of the developer API provided by different MOMs are the same. It’s this similarity in APIs that makes the Java Message Service possible. The Java Message Service (JMS) is a vendor-agnostic Java API that can be used with many different MOM vendors. JMS is very similar to JDBC in that application developer reuses the same API to access many different systems. If a vendor provides a compliant service provider for JMS, then the JMS API can be used to send and receive messages to that vendor. For example, you can use the same JMS API to send messages using Progress SonicMQ as you do IBM s MQSeries. Message-Driven Beans All JMS vendors provide application developers with the same API for sending and receiving messages, and sometimes they provide a component model for developing routers that can receive and send messages. These component models, however, are proprietary and not portable across MOM vendors. Enterprise JavaBeans 2.0 introduces a new kind of component, called a message-driven bean, which is a kind of standard JMS bean. It can receive and send asynchronous JMS messages, because it s co-located with other kinds of RMI beans (entity and session beans) it can also interact with RMI components. Message-driven beans in EJB 2.0 act as an integration point for a EJB application, allowing other applications to asynchronous messages which can be captured and processed by an EJB application. This is an extremely important feature that will allow EJB applications to better integrate with legacy and other proprietary systems. Message-driven beans are also transactional and required all the infrastructure associated with other RMI based transactional server-side components. Like other RMI based components, message-driven beans are considered business objects, which full fill an important role of routing and interpreting requests and coordinating the application of those requests against other RMI based components, namely enterprise beans. Message- driven beans are a good fit for the component transaction manager landscape and are an excellent addition to the Enterprise JavaBeans platform. Copyright (c) 2001 O’Reilly & Associates
Do you want something as professional as you are? Well, we are, but our plans are even better, please check Web Hosting SSH and look why we are the best.