- (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches
- (JMS_SPEC-46) Define standard API to create and configure a ConnectionFactory
- (JMS_SPEC-6) Add Reference to SOAP Binding
- (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE
- (JMS_SPEC-64) Define simplified JMS API
- (JMS_SPEC-67) Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- (JMS_SPEC-7) Provide HTTP Binding
- (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container
- (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way
- [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jsr343-experts] (JMS_SPEC-6) Add Reference to SOAP Binding
- [jsr343-experts] (JMS_SPEC-7) Provide HTTP Binding
- [jsr343-experts] (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container
- [jsr343-experts] (JMS_SPEC-9) Support for AMQP messaging
- [jsr343-experts] (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way
- [jsr343-experts] (JMS_SPEC-93) Does changing the noLocal flag when connecting to a durable subscription cause the durable subscription to be deleted?
- [jsr343-experts] [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jsr343-experts] JMS 2.0: Planning the next stage
- [jsr343-experts] Revised schedule for JSR 343
- [jsr343-experts] Why are Destinations resources and not Strings?
- JMS 2.0 Early Draft is posted
- JMS 2.0 Early Draft ready for final review
- JMS 2.0: Planning the next stage
- Poison Message Handling
- Why are Destinations resources and not Strings?
- Last message date: Fri Mar 30 17:55:13 2012
- Archived on: Thu Aug 10 15:14:55 2017 PDT