JavaMessageService 2.0规范详解

4星 · 超过85%的资源需积分: 10 44 浏览量更新于2024-07-28 1 收藏 949KB PDF 举报

"Java Message Service (JMS) 2.0规范是Java程序访问企业消息系统的API的最新版本。此规范由Mark Hapner、Rich Burridge、Rahul Sharma、Joseph Fialli和Kate Stout等人编写，是Oracle公司对1.0.2版本的更新，旨在提供更先进的消息传递功能和改进的接口设计。" JMS 2.0规范详解： 1. **版本升级**：JMS 2.0相对于1.0.2版本进行了重大更新，引入了更多现代化的特性以适应不断变化的开发需求。主要目的是提高开发者在处理分布式消息传递时的效率和便利性。 2. **简化API**：JMS 2.0简化了消息生产者和消费者的创建过程，通过引入`MessageProducer`和`MessageConsumer`的默认行为，使得发送和接收消息变得更加简单。 3. **核心API增强**：在JMS 2.0中，`Message`接口新增了发送和接收消息的批处理支持，允许一次性处理多个消息，提高了性能。同时，支持了消息预定义的属性，增强了消息的可读性和可操作性。 4. **消息订阅的持久化**：JMS 2.0提供了更强大的订阅持久化机制，即使在消费者应用程序重启后，也能恢复未处理的消息，确保消息的不丢失。 5. **共享订阅**：新规范引入了共享订阅的概念，允许多个消费者共享同一个订阅，从而实现负载均衡和高可用性。 6. **主题的多发布者模式**：JMS 2.0支持多个生产者向同一个主题发布消息，这在多服务协作和事件驱动架构中非常有用。 7. **消息传递保证**：JMS 2.0继续提供四种消息传递模式：点对点（Queue）、发布/订阅（Topic）、事务（Transacted）和持久化（Persistent），以满足不同业务场景的需求。 8. **安全和管理**：规范中详细阐述了如何实现JMS服务的安全控制和管理，包括认证、授权和审计等，确保了消息传递的安全性。 9. **互操作性**：JMS 2.0旨在保持与其他JMS实现的兼容性，同时提供新的API以便于不同供应商之间的互操作。 10. **文档和社区**：JMS 2.0规范的发布伴随着详尽的文档，以及活跃的用户社区（users@jms-spec.java.net），为开发者提供了丰富的参考资料和技术支持。 JMS 2.0规范不仅提供了更强大的消息处理能力，还优化了开发者体验，是现代Java应用进行企业级消息通信的重要工具。对于希望深入了解和应用JMS的开发者来说，熟悉这个规范至关重要。

16 Java Message Service Version 2.0 (Early Draft)

• Batch delivery: new API has been added to allow a JMS provider to

deliver messages to an asynchsonous consumer in batches.

• Delivery delay: a message producer can now specify that a message

must not be delivered until after a specified time interval.

• New send methods have been added to allow an application to send

messages asynchronously.

• JMS providers must now set the JMSXDeliveryCount message

property.

Several changes have been made to the JMS API to make it simpler and

easier to use:

• Connection, Session and other objects with a close() method

now implement the java.jang.AutoCloseable interface to allow

them to be used in a Java SE 7 try-with-resources starement.

• A new "simplified API" has been added which offers a simpler

alternative to the standard API, especially in Java EE applications.

• New methods have been added to create a session without the need to

supply redundant arguments.

• Client ID is now optional when creating a durable subscription

A new chapter has been added which describes some additional

restrictions and behaviour which apply when using the JMS API in the

Java EE web or EJB container. This information was previously only

available in the EJB and Java EE platform specifications.

New methods have been added to Session which return a

MessageConsumer on a durable topic subscription. Applications could

previously only obtain a domain-specific TopicSubscriber, even

though its use was discouraged.

The specification has been clarified in various places.

2. Architecture 17

2. Architecture

2.1. Overview

This chapter describes the environment of message based applications and

the role JMS plays in this environment.

2.2. What is a JMS application?

A JMS application is composed of the following parts:

• JMS Clients - These are the Java language programs that send and

receive messages.

• Non-JMS Clients - These are clients that use a message systems

native client API instead of JMS. If the application predated the

availability of JMS it is likely that it will include both JMS and non-

JMS clients.

• Messages - Each application defines a set of messages that are used to

communicate information between its clients.

• JMS Provider - This is a messaging system that implements JMS in

addition to the other administrative and control functionality required

of a full featured messaging product.

• Administered Objects - Administered objects are preconfigured JMS

objects created by an administrator for the use of clients.

2.3. Administration

It is expected that each JMS provider will differ significantly in their

underlying messaging technology. It is also expected there will be major

differences in how a provider’s system is installed and administered.

If JMS clients are to be portable, they must be isolated from these

proprietary aspects of a provider. This is done by defining JMS

administered objects that are created and customized by a provider’s

administrator and later used by clients. The client uses them through JMS

interfaces that are portable. The administrator creates them using provider-

specific facilities.

There are two types of JMS administered objects:

•

ConnectionFactory - This is the object a client uses to create a

connection with a provider.

•

Destination - This is the object a client uses to specify the

destination of messages it is sending and the source of messages it

receives.

Administered objects are placed in a JNDI namespace by an administrator.

A JMS client typically notes in its documentation the JMS administered

objects it requires and how the JNDI names of these objects should be

provided to it. Figure 2.1 illustrates how JMS administration ordinarily

works.

剩余147页未读，继续阅读

sghfofo

粉丝: 2
资源: 10

JavaMessageService 2.0规范详解

JMS 2.0规范详解：Java企业消息系统接入

JavaMessageService 2.0 API：规范与应用

RocketMQ开发指南：消费打印日志优化与关键技术

JMS 2.0 规范

jms规范2.0（中英文都有）

全面研读EJB2.0规范

javax.jms包,sun的JMS接口规范包

Swift 2.0语言规范(官方英文版)

EJB2.0

ejb2.0.rar_EJB2.0特性_ejb2.0

最新资源