Answer Posted / munnu
When the JMS API was introduced in 1998, its most important purpose was to allow Java applications to access existing messaging-oriented middleware (MOM) systems, such as MQSeries from IBM. Since that time, many vendors have adopted and implemented the JMS API, so that a JMS product can now provide a complete messaging capability for an enterprise.
Since the 1.3 release of the J2EE platform ("the J2EE 1.3 platform"), the JMS API has been an integral part of the platform, and application developers can use messaging with components using J2EE APIs ("J2EE components").
The JMS API in the J2EE platform has the following features.
* Application clients, Enterprise JavaBeans (EJB) components, and Web components can send or synchronously receive a JMS message. Application clients can in addition receive JMS messages asynchronously. (Applets, however, are not required to support the JMS API.)
* Message-driven beans, which are a kind of enterprise bean, enable the asynchronous consumption of messages. A JMS provider may optionally implement concurrent processing of messages by message-driven beans.
* Message sends and receives can participate in distributed transactions.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What are the different places where you can use the JMS API?
How do I check messages in jms queue?
How many types of messaging model do JMS provide for and what are they?
What is jms mean?
What are the three parts of the message?
Which types of jdbc databases does weblogic jms support?
What is a connection factory?
How to write junit test cases for jms?
What type of messaging is provided by JMS?
What are the functionalities of a jms provider?
How do I use a third-party jdbc driver with jms?
How can an application do a jms operation and have it succeed, independent of the result of the transaction?
Explain JMS and its Component?
How to Allowe messages to expire ?
What is message listener container?