JMS 2.0 Planning
This page contains lists of issues which were resolved in JMS 2.0.
Contents
- All issues incorporated in the JMS 2.0 final release
- Issues incorporated in the early draft
- Additional issues incorporated in the public draft.
- Additional issues incorporated in the proposed final draft
- Additional issues incorporated in the final release
- Issues resolved by updates to the Java EE 7 specification
- Issues resolved by updates to the Java Connector Architecture 1.7 specification
- Related pages
All issues incorporated in the JMS 2.0 final release
Issues Issues are listed by the draft in which they were resolved.
- Query: All issues resolved in the early draft
- Query: All additional issues resolved in the public draft
- Query: All additional issues resolved in the final draft
- Query: All additional issues resolved in the final release
Issues incorporated in the early draft
Query: All issues resolved in the early draft
| ID | Description | Notes |
|---|---|---|
| JMS_SPEC-65 | Clarify use of NoLocal arg when using createDurableSubscriber | This was introduced into the Early Draft and further updated for the Public Draft. |
| JMS_SPEC-53 | Make Connection and other interfaces implement AutoCloseable | |
| JMS_SPEC-52 | Clarify that a message may be sent using a different session from that used to create the message | |
| JMS_SPEC-51 | New methods to replace Session.createDurableSubscriber() and return a MessageConsumer | |
| JMS_SPEC-50 | Clarify that JMS providers must implement both P2P and Pub-Sub | In the Early Draft |
| JMS_SPEC-49 | Improve specification of ExceptionListener | |
| JMS_SPEC-48 | Specify that connection.stop() or close() may not be called from MessageListener | |
| JMS_SPEC-45 | Clarify and improve Connection.createSession | |
| JMS_SPEC-44 | New API to specify delivery delay | |
| JMS_SPEC-43 | New API to send a message with async acknowledgement from server | This was introduced into the Early Draft and further updated for the Public Draft. JMS_SPEC-12 is a duplicate of this. |
| JMS_SPEC-42 | Make support for JMSXDeliveryCount mandatory | |
| JMS_SPEC-39 | Make clientId optional when creating a durable subscription | Shared subscriptions only |
| JMS_SPEC-34 | Calling setJMSDeliveryMode or setJMSPriority on a javax.jms.Message before it is sent don’t have any effect | |
| JMS_SPEC-33 | Improving the JMS API with API simplifications, annotations and CDI | |
| JMS_SPEC-27 | Clarify the relationship between the JMS and other Java EE specifications | |
| JMS_SPEC-12 | Message producer confirms aka async message production. | Duplicate of JMS_SPEC-43 |
Additional issues incorporated in the public draft.
Query: All additional issues resolved in the public draft
| ID | Description | Notes |
|---|---|---|
| JMS_SPEC-107 | Extend connection consumer API to support shared durable and non-durable subscriptions | |
| JMS_SPEC-106 | Methods on JMSContext that are disallowed if the context is injected should throw a IllegalStateException not a JMSException | |
| JMS_SPEC-105 | Provide API to allow an app server or resource adapter to obtain a XAResource from a JMSContext | |
| JMS_SPEC-102 | Make JMSConsumer.receivePayload methods consistent with Message.getBody | |
| JMS_SPEC-101 | New method Message.getBody | |
| JMS_SPEC-98 | Fix findbugs warnings in JMSException, JMSRuntimeException, QueueRequestor, TopicRequestor | RI rather than spec issue, resolved |
| JMS_SPEC-97 | This was introduced into the public draft and further updated for the proposed final draft and the final release. Annotations are defined in JMS, descriptor elements are defined in the Java EE schema | |
| JMS_SPEC-96 | Define Java EE JMS Connection Factory Definition annotation and descriptor elements | This was introduced into the public draft and further updated for the proposed final draft and the final release. Annotations are defined in JMS, descriptor elements are defined in the Java EE schema. |
| JMS_SPEC-94 | Define what characters are valid in a durable (or shared subscription) name | |
| JMS_SPEC-93 | Does changing the noLocal flag when connecting to a durable subscription cause the durable subscription to be deleted? | |
| JMS_SPEC-82 | Clarify definition of JMSExpiration, replacing GMT with UTC | |
| JMS_SPEC-80 | Error in example 9.3.3.2 “Reconnect to a topic using a durable subscription” | |
| JMS_SPEC-78 | JMS implementation of QueueRequestor and TopicRequestor doesn’t throw correct exception when destination is null | RI rather than spec issue, resolved |
| JMS_SPEC-77 | MapMessage.setBytes API discrepancy found in the javadocs | |
| JMS_SPEC-70 | Define annotations for injecting MessagingContext objects | |
| JMS_SPEC-64 | Define simplified JMS API | |
| JMS_SPEC-40 | Allow multiple consumers to be created on the same topic subscription | |
| JMS_SPEC-31 | change javadoc on session.createQueue and createTopic to make clearer the provider may create a physical destination |
Additional issues incorporated in the proposed final draft
Query: All additional issues resolved in the final draft
| ID | Description | Notes |
|---|---|---|
| JMS_SPEC-115 | Remove the statement that portable applications should only have one consumer per queue | |
| JMS_SPEC-114 | Clarify javadoc descriptions of XAQueueConnection#createSession and XATopicSession#createSession | |
| JMS_SPEC-87 | Section 2.5 “Interfaces” needs updating to introduce the simplified API | |
| JMS_SPEC-81 | Remove Change History for previous versions from the specification | |
| JMS_SPEC-69 | Clarify that QueueRequestor and TopicRequestor only work in a non-transacted session with auto or dups-ok ack | |
| JMS_SPEC-55 | Define a standard way to configure the connection factory used by a JMS MDB to consume messages | Now covered in a new JMS 2.0 chapter “Resource adapter”. Text also added to EJB 3.2 specification. |
| JMS_SPEC-54 | Define a standard way to configure the destination on which a JMS MDB consumes messages | Now covered in a new JMS 2.0 chapter “Resource adapter”. Text also added to EJB 3.2 specification. |
| JMS_SPEC-30 | Define mandatory activation config properties clientId and subscriptionName | Text also added to EJB 3.2 specification. |
Additional issues incorporated in the final release
Query: All additional issues resolved in the final release
| ID | Description | Notes |
|---|---|---|
| JMS_SPEC-86 | Chapter 1 “Introduction” is a little dated and requires rewriting | |
| JMS_SPEC-63 | Introduce concept of platform default JMS connection factory in Java EE | Included in Java EE 7 specification. |
Issues resolved by updates to the Java EE 7 specification
| ID | Description | Notes |
|---|---|---|
| JMS_SPEC-63 | Introduce concept of platform default JMS connection factory in Java EE | Included in Java EE 7 specification. |
Issues resolved by updates to the Java Connector Architecture 1.7 specification
| ID | Description | Notes |
|---|---|---|
| CONNECTOR_SPEC-4 | Clarify whether the ResourceAdapter.endpointActivation call has full access to administered objects in JNDI | Agreed by JCA EG. Needed for JMS_SPEC-54 and JMS_SPEC-55 |