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 types of messages that are supported by JMS?
What is ems queue?
What is the difference between JMS and RPC (Remote Procedure Call)?
What is jms connection?
What is difference between queue and topic?
In which situations we are using jms? Can we send message from one server to another server using jms?
What is a remote jms provider?
Can we have more than one consumer for a jms queue?
What is jms publisher?
What is the difference between java mail and jms queue?
What is a JMS client?
How do the wls jms 6.1 server/destination message maximum and threshold values work?
How do I configure jms security?
What is jms producer?
Is kafka a jms?