- (JMS_SPEC-36) Allow messages to be delivered asyncrhonously in batches
- (JMS_SPEC-39) Make clientId optional when creating a durable subscription
- (JMS_SPEC-40) Allow multiple consumers to be created on the same topic subscription (note new summary line)
- (JMS_SPEC-43) New API to send a message with async acknowledgement from server
- (JMS_SPEC-45) Clarify and improve Connection.createSession
- (JMS_SPEC-46) Define standard API to create and configure a ConnectionFactory
- (JMS_SPEC-47) Deprecate domain-specific APIs and propose for removal
- (JMS_SPEC-48) Specify that connection.stop() or close() may not be called from a MessageListener
- (JMS_SPEC-49) Improve specification of ExceptionListener
- (JMS_SPEC-50) Clarify that JMS providers must implement both P2P and Pub-Sub
- (JMS_SPEC-51) Change Session.createDurableSubscriber() to return a MessageConsumer
- (JMS_SPEC-52) Clarify that a message may be sent using a different session from that used to create the message
- [jms-spec users] (JMS_SPEC-52) Clarify that a message may be sent using a different session from that used to create the message
- [jsr343-experts] (JMS_SPEC-51) Change Session.createDurableSubscriber() to return a MessageConsumer
- [jsr343-experts] (JMS_SPEC-52) Clarify that a message may be sent using a different session from that used to create the message
- [jsr343-experts] JMS 2.0 at JavaOne
- [jsr343-experts] JMS Object Scopes
- [jsr343-experts] Make Connection, Session and other interfaces implement AutoCodeable
- [jsr343-experts] MessageApi proposal
- JMS 2.0 at JavaOne
- JMS 2.0 Event Messaging
- JMS 2.0 Event Messaging (again!)
- JMS Object Scopes
- JMS Support for DI
- Make Connection, Session and other interfaces implement AutoCodeable
- {JMS_SPEC-30} Define mandatory activation config properties for JMS MDBs
- Last message date: Thu Sep 29 12:14:40 2011
- Archived on: Thu Aug 10 15:14:55 2017 PDT