Answer / 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.

What is jms protocol?

0 Answers  

---

Can you use a foreign jms provider to drive an mdb transactionally?

0 Answers  

---

Is jms a protocol?

0 Answers  

---

Why do we use message queue?

0 Answers  

---

How the jms is different from rpc?

0 Answers  

---

Explain about the exception handling mechanism of JMS?

0 Answers  

---

What is a bytes message?

0 Answers  

---

What is Stream Message ?

1 Answers   CAP,

---

What is asynchronous messaging?

0 Answers  

---

How does a sender application transport/send a message through jms?

0 Answers  

---

What type messaging is provided by JMS ?

1 Answers  

---

What is asynchronous messaging in jms?

0 Answers  

---