1)recap
The Message
interface is the root interface of all JMS messages. It defines the message header and the acknowledge
method used for all messages.
Most message-oriented middleware (MOM) products treat messages as lightweight entities that consist of a header and a payload. The header contains fields used for message routing and identification; the payload contains the application data being sent.
Within this general form, the definition of a message varies significantly across products. It would be quite difficult for the JMS API to support all of these message models.
With this in mind, the JMS message model has the following goals:
- Provide a single, unified message API
- Provide an API suitable for creating messages that match the format used by provider-native messaging applications
- Support the development of heterogeneous applications that span operating systems, machine architectures, and computer languages
- Support messages containing objects in the Java programming language ("Java objects")
- Support messages containing Extensible Markup Language (XML) pages
JMS messages are composed of the following parts:
- Header - All messages support the same set of header fields. Header fields contain values used by both clients and providers to identify and route messages.
- Properties - Each message contains a built-in facility for supporting application-defined property values. Properties provide an efficient mechanism for supporting application-defined message filtering.
- Body - The JMS API defines several types of message body, which cover the majority of messaging styles currently in use.
2) Message Header
The JMSCorrelationID
header field is used for linking one message with another. It typically links a reply message with its requesting message.
JMSCorrelationID
can hold a provider-specific message ID, an application-specific String
object, or a provider-native byte[]
value.
3)Message Properties
相关推荐
是一个快速的开源消息组件(框架),支持集群,同等网络,自动检测,TCP,SSL,广播,持久化,XA,和J2EE1.4容器无缝结合,并且支持轻量级容器和大多数跨语言客户端上的Java虚拟机。消息异步接受,减少软件多系统集成...
jms资料 Message Queue 3 技术概述
Message Owl:Eclipse JMS 队列和主题工具 Message Owl是一个基于的工具,可帮助使用 Eclipse 的人与基于的消息队列进行交互。 Message Owl可以添加到任何已经包含的安装中。 如果您是从头开始,最简单的方法是下载...
It starts from the anatomy of a JMS message and moves quickly through connectors, message persistence, authentication, and authorization. By following a running example (a stock portfolio app), you'...
NULL 博文链接:https://elim.iteye.com/blog/1900937
javax.jms.Message.class javax.jms.MessageConsumer.class javax.jms.MessageEOFException.class javax.jms.MessageFormatException.class javax.jms.MessageListener.class javax.jms.MessageNotReadableException...
The book lays out the core of ActiveMQ in clear language, starting with the anatomy of a JMS message and moving quickly through connectors, message persistence, authentication and authorization....
JMS ,java message service 消息中间件开源项目幻灯片
javax.jms.Message.class javax.jms.JMSException.class javax.jms.Destination.class javax.jms.DeliveryMode.class javax.jms.Connection.class javax.jms.Session.class javax.jms.ConnectionMetaData.class ...
nents has never been easier, because you don’t have to implement JMS message listeners or FTP clients, deal with converting data between protocols, or mess with the raw details of ...
关于JMS的消息服务的代码,包括PTP和Pub/Sub,简单通俗 易懂。
JMS(Java Message Service)是访问企业消息系统的标准API,它便于消息系统中的Java应用程序进行消息交换,并且通过提供标准的产生、发送、接收消息的接口简化企业应用的开发。
JMS (Java Message Service): Queue, Topic两种模式
zip包中包含jms-1_1-fr-apidocs.zip和geronimo-jms_1.1_spec-1.1.1.jar。使用jms-1_1-fr-apidocs.zip与geronimo-jms_1.1_spec-1.1.1.jar可替换
Java+Message+Service+JMS+java消息服务
JMS接收端所需要用到的jar包,如果有需要得朋友就下载吧,发送端暂时不发以后再发。
一篇深入的讲解了java message service技术的文档 ,希望对大家有所帮助
nents has never been easier, because you don’t have to implement JMS message listeners or FTP clients, deal with converting data between protocols, or mess with the raw details of ...
JMS : Java Message Service (Java消息服务)1 引言 1.1 编写目的 1.2 名词解释
2.3.3. Anatomy of a JMS Message ............................................ 33 2.3.4. Message Selectors ........................................................... 40 2.3.5. JMS Domains ................