datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

URI Scheme for Java(tm) Message Service 1.0
draft-merrick-jms-uri-12

RFC
Document Stream: IETF
Last updated: 2011-01-20
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6167
IANA Action State: RFC-Ed-Ack 
Responsible AD: Alexey Melnikov
Send notices to: eric@tibco.com, m8philli@uk.ibm.com, phil_adams@us.ibm.com, derek.rokicki@softwareag.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-merrick-jms-uri.

Abstract:
This document defines the format of Uniform Resource Identifiers (URIs) as defined in RFC 3986, for designating connections and destination addresses used in the Java(tm) Messaging Service (JMS). It was originally designed for particular uses, but applies generally wherever a JMS URI is needed to describe the connection to a JMS provider, and access to a JMS Destination. The syntax of this JMS URI is not compatible with previously existing, but unregistered, "jms" URI schemes. However, the expressiveness of the scheme described herein should satisfy the requirements of all existing circumstances. This document is not an Internet Standards Track specification; it is published for informational purposes.

Authors:
Eric Johnson <eric@tibco.com>
Derek Rokicki <derek.rokicki@softwareag.com>
Phil Adams <phil_adams@us.ibm.com>
Mark Phillips <m8philli@uk.ibm.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)