JavaJEEJMS: Difference between revisions

From Wiki RB4
(New page: ==Introduction== The Java Message Service (JMS) API is a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, rece...)
 
 
Line 1: Line 1:
==Introduction==
==Introduction==
The Java Message Service (JMS) API is a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
The Java Message Service (JMS) API is a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous. The JMS API supports two models:
 
* point-to-point or queuing model (post message to a particular queue)  
Concepts are:
* publish and subscribe model (post a message for a topic)
* JMS producer
* JMS consumer
* JMS client (producer and consumer)
* JMS queue
* JMS topic (distribution mechanismen to publish messages to subscribers)


A JMS message has three parts:
* A header
* Properties (optional)
* A body (optional)


Version 1.1 of the JMS API in the J2EE 1.4 platform has the following features:  
Version 1.1 of the JMS API in the J2EE 1.4 platform has the following features:  
Line 18: Line 17:
* 1.0 June 2001
* 1.0 June 2001
* 1.1 March 2002
* 1.1 March 2002


==Resources==
==Resources==

Latest revision as of 13:38, 21 July 2008

Introduction[edit]

The Java Message Service (JMS) API is a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous. The JMS API supports two models:

  • point-to-point or queuing model (post message to a particular queue)
  • publish and subscribe model (post a message for a topic)

A JMS message has three parts:

  • A header
  • Properties (optional)
  • A body (optional)

Version 1.1 of the JMS API in the J2EE 1.4 platform has the following features:

  • Message-driven beans enable the asynchronous consumption of JMS messages.
  • Message sends and receives can participate in Java Transaction API (JTA) transactions.
  • J2EE Connector Architecture interfaces that allow JMS implementations from different vendors to be externally plugged into a J2EE 1.4 application server.

Versions[edit]

  • 1.0 June 2001
  • 1.1 March 2002

Resources[edit]