- (JMS_SPEC-101) New method Message.getBody(Class<T> c)
- (JMS_SPEC-101) New method Message.getPayload(Class<T> c)
- (JMS_SPEC-102) Make JMSConsumer.receivePayload methods consistent with Message.getBody
- (JMS_SPEC-105) Provide API to allow an app server or resource adapter to obtain a XAResource from a JMSContext
- (JMS_SPEC-109) add method Destination.getName()
- (JMS_SPEC-112) add Message.getJMSDeliveryCount()
- (JMS_SPEC-114) Clarify javadoc descriptions of XAQueueConnection#createSession and XATopicSession#createSession
- (JMS_SPEC-115) Remove the statement that portable applications should only have one consumer per queue
- (JMS_SPEC-116) Take advantage of EJB 3.2's RA improvement for MDBs
- (JMS_SPEC-121) Injection of JMSContext objects not possible in a WebSocket @OnMessage or @OnClose callback method
- (JMS_SPEC-25) Standardise the interface between a JMS provider and a Java EE application server
- (JMS_SPEC-26) Decide on the future of the optional Chapter 8 API "JMS Appli
- (JMS_SPEC-26) Decide on the future of the optional Chapter 8 API "JMS Application Server Facilities"
- (JMS_SPEC-28) Clarify how the JMS provider should interact with Transaction Managers.
- (JMS_SPEC-31) Allow session.createQueue and createTopic to create server side destinations case they don't exist
- (JMS_SPEC-33) Improving the JMS API with API simplifications, annotations and CDI
- (JMS_SPEC-34) Calling setJMSDeliveryMode or setJMSPriority on a javax.jms.Message before it is sent don't have any effect
- (JMS_SPEC-35) Remove the use of unchecked exceptions from the JMS API as far as possible
- (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches
- (JMS_SPEC-36) Allow messages to be delivered asyncrhonously in batches
- (JMS_SPEC-38) Allow JMS clients to specify whether a message is compressed in transit
- (JMS_SPEC-39) Make clientId optional when creating a durable subscription
- (JMS_SPEC-4) Properties on Messages should follow builder pattern.
- (JMS_SPEC-40) Allow multiple consumers to be created on the same topic subscription
- (JMS_SPEC-40) Allow multiple consumers to be created on the same topic subscription (note new summary line)
- (JMS_SPEC-40) Allow multiple threads in same client to consume messages from the same topic subscription
- (JMS_SPEC-40) Dropping noLocal from shared subscriptions
- (JMS_SPEC-40) Meaning of noLocal with shared non-durable subscriptions
- (JMS_SPEC-42) Make support for JMSXDeliveryCount mandatory
- (JMS_SPEC-43) New API to send a message with async acknowledgement from server
- (JMS_SPEC-44) New API to specify delivery delay
- (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) Rules on calling consumer.close()
- (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-54) Define a standard way to configure the destination on which a MDB consumes messages
- (JMS_SPEC-55) Define a standard way to configure the connection factory used by a JMS MDB to consume messages
- (JMS_SPEC-56) Enhance the EJB specification to support the delivery of messages in batches to MDBs
- (JMS_SPEC-57) Add Java EE 7 multi-tenancy support
- (JMS_SPEC-6) Add Reference to SOAP Binding
- (JMS_SPEC-61) Selector on JMS body
- (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE
- (JMS_SPEC-64) Define simplified JMS API
- (JMS_SPEC-64) Define simplified JMS API (CDI questions)
- (JMS_SPEC-65) Clarify use of NoLocal arg when using createDurableSubscriber
- (JMS_SPEC-67) Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- (JMS_SPEC-68) Add new method Session.acknowledge()
- (JMS_SPEC-69) Clarify that QueueRequestor and TopicRequestor only work in a non-transacted session with auto or dups-ok ack
- (JMS_SPEC-7) Provide HTTP Binding
- (JMS_SPEC-70) Define annotations for injecting JMSContext objects
- (JMS_SPEC-70) Define annotations for injecting MessagingContext objects
- (JMS_SPEC-73) Define how messages from a topic are delivered to clustered application server instances
- (JMS_SPEC-77) MapMessage.setBytes API discrepancy found in the javadocs
- (JMS_SPEC-86) Chapter 1 "Introduction" is a little dated and requires rewriting
- (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-94) Define what characters are valid in a durable (or shared subscription) name
- (JMS_SPEC-96 & 97) Define Java EE connection factory and destination definition annotations and descriptor elements
- [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jms-spec issues] [JIRA] Created: (JMS_SPEC-54) Define a standard way to configure the destination on which a MDB consumes messages
- [jms-spec users] (JMS_SPEC-121) Injection of JMSContext objects not possible in a WebSocket @OnMessage or @OnClose callback method
- [jms-spec users] (JMS_SPEC-144) StreamMessage#getBody(Class<T>)
- [jms-spec users] (JMS_SPEC-35) Remove the use of unchecked exceptions from the JMS API as far as possible
- [jms-spec users] (JMS_SPEC-43) New API to send a message with async acknowledgement from server
- [jms-spec users] (JMS_SPEC-52) Clarify that a message may be sent using a different session from that used to create the message
- [jms-spec users] Discussion point: deadlocks in MessageListener and ExceptionListener
- [jms-spec users] Individual Client ACK
- [jms-spec users] JMS 2.0 Priorities: Proposal from Adrian Johnson and Shivajee Samdarshi (TIBCO Software Inc.)
- [jms-spec users] JMS 2.0 Priorities: Proposal from Emran Shaik
- [jms-spec users] JMS 2.0 Priorities: Proposal from Julien Dubois
- [jms-spec users] JMS at JavaOne
- [jms-spec users] JMS over CDI or something else?
- [jms-spec users] jms2.0 spec adoption into glassfish
- [jms-spec users] JMSProducer#getProperyNames()
- [jms-spec users] JSR 343: Summary of priorities so far
- [jms-spec users] Late change: A.3.2 Meaning of noLocal with shared topic subscriptions
- [jms-spec users] Make TemporaryQueue/Topic AutoCloseable?
- [jms-spec users] State of a message in a producer after send
- [jms-spec users] Welcome Rob Davies
- [jms-spec users] Welcome Sastry Malladi!
- [jsr343-experts] (JMS_SPEC-101) New method Message.getPayload(Class<T> c)
- [jsr343-experts] (JMS_SPEC-102) Make JMSConsumer.receivePayload methods consistent with Message.getBody
- [jsr343-experts] (JMS_SPEC-105) Provide API to allow an app server or resource adapter to obtain a XAResource from a JMSContext
- [jsr343-experts] (JMS_SPEC-106) Methods on JMSContext that are disallowed if the context is injected should throw a IllegalStateException not a JMSException
- [jsr343-experts] (JMS_SPEC-107) Extend connection consumer API to support shared durable and non-durable subscriptions
- [jsr343-experts] (JMS_SPEC-108) add generics to methods currently returning raw types
- [jsr343-experts] (JMS_SPEC-109) add method Destination.getName()
- [jsr343-experts] (JMS_SPEC-112) add Message.getJMSDeliveryCount()
- [jsr343-experts] (JMS_SPEC-115) Remove the statement that portable applications should only have one consumer per queue
- [jsr343-experts] (JMS_SPEC-116) Take advantage of EJB 3.2's RA improvement for MDBs
- [jsr343-experts] (JMS_SPEC-119) Remove reference to password alias
- [jsr343-experts] (JMS_SPEC-121) Injection of JMSContext objects not possible in a WebSocket @OnMessage or @OnClose callback method
- [jsr343-experts] (JMS_SPEC-25) Standardise the interface between a JMS provider and a Java EE application server
- [jsr343-experts] (JMS_SPEC-26) Decide on the future of the optional Chapter 8 API "JMS Application Server Facilities"
- [jsr343-experts] (JMS_SPEC-27) Clarify the relationship between the JMS and other Java EE specifications
- [jsr343-experts] (JMS_SPEC-28) Clarify how the JMS provider should interact with Transaction Managers.
- [jsr343-experts] (JMS_SPEC-33) Improving the JMS API with API simplifications, annotations and CDI
- [jsr343-experts] (JMS_SPEC-34) Calling setJMSDeliveryMode or setJMSPriority on a javax.jms.Message before it is sent don't have any effect
- [jsr343-experts] (JMS_SPEC-35) Remove the use of unchecked exceptions from the JMS API as far as possible
- [jsr343-experts] (JMS_SPEC-36) Allow messages to be delivered asyncrhonously in batches
- [jsr343-experts] (JMS_SPEC-38) Allow JMS clients to specify whether a message is compressed in transit
- [jsr343-experts] (JMS_SPEC-39) Make clientId optional when creating a durable subscription
- [jsr343-experts] (JMS_SPEC-4) Properties on Messages should follow builder pattern.
- [jsr343-experts] (JMS_SPEC-40) Allow multiple threads in same client to consume messages from the same topic subscription
- [jsr343-experts] (JMS_SPEC-41) Support topic hierarchies
- [jsr343-experts] (JMS_SPEC-42) Make support for JMSXDeliveryCount mandatory
- [jsr343-experts] (JMS_SPEC-43) New API to send a message with async acknowledgement from server
- [jsr343-experts] (JMS_SPEC-44) New API to specify delivery delay
- [jsr343-experts] (JMS_SPEC-45) Clarify and improve Connection.createSession
- [jsr343-experts] (JMS_SPEC-46) Define standard API to create and configure a ConnectionFactory
- [jsr343-experts] (JMS_SPEC-47) Deprecate domain-specific APIs and propose for removal
- [jsr343-experts] (JMS_SPEC-48) Specify that connection.stop() or close() may not be called from a MessageListener
- [jsr343-experts] (JMS_SPEC-49) Improve specification of ExceptionListener
- [jsr343-experts] (JMS_SPEC-50) Clarify that JMS providers must implement both P2P and Pub-Sub
- [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_SPEC-54) Define a standard way to configure the destination on which a MDB consumes messages
- [jsr343-experts] (JMS_SPEC-55) Define a standard way to configure the connection factory used by a JMS MDB to consume messages
- [jsr343-experts] (JMS_SPEC-56) Enhance the EJB specification to support the delivery of messages in batches to MDBs
- [jsr343-experts] (JMS_SPEC-57) Add Java EE 7 multi-tenancy support
- [jsr343-experts] (JMS_SPEC-6) Add Reference to SOAP Binding
- [jsr343-experts] (JMS_SPEC-61) Selector on JMS body
- [jsr343-experts] (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE
- [jsr343-experts] (JMS_SPEC-64) Define simplified JMS API
- [jsr343-experts] (JMS_SPEC-65) Clarify use of NoLocal arg when using createDurableSubscriber
- [jsr343-experts] (JMS_SPEC-67) Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- [jsr343-experts] (JMS_SPEC-68) Add new method Session.acknowledge()
- [jsr343-experts] (JMS_SPEC-69) Clarify that QueueRequestor and TopicRequestor only work in a non-transacted session with auto or dups-ok ack
- [jsr343-experts] (JMS_SPEC-7) Provide HTTP Binding
- [jsr343-experts] (JMS_SPEC-70) Define annotations for injecting MessagingContext objects
- [jsr343-experts] (JMS_SPEC-73) Define how messages from a topic are delivered to clustered application server instances
- [jsr343-experts] (JMS_SPEC-77) MapMessage.setBytes API discrepancy found in the javadocs
- [jsr343-experts] (JMS_SPEC-80) Error in example 9.3.3.2 "Reconnect to a topic using a durable subscription"
- [jsr343-experts] (JMS_SPEC-86) Chapter 1 "Introduction" is a little dated and requires rewriting
- [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-94) Define what characters are valid in a durable (or shared subscription) name
- [jsr343-experts] (JMS_SPEC-96 & 97) Define Java EE connection factory and destination definition annotations and descriptor elements
- [jsr343-experts] (JMS_SPEC-98) Fix findbugs warnings in JMSException, JMSRuntimeException, QueueRequestor, TopicRequestor
- [jsr343-experts] [ADMIN] Starting discussions
- [jsr343-experts] [Admin]JIRA issues, handy JIRA query
- [jsr343-experts] [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jsr343-experts] Batch Messages really abandoned?
- [jsr343-experts] Batch processing...
- [jsr343-experts] Can I start work on JMS 2.1 spec changes for the ACK mode related issues?
- [jsr343-experts] CDI Support in JMS 2.0
- [jsr343-experts] Clarification about JMSContext and setClientID
- [jsr343-experts] Clarification on JMSContext::createConsumer
- [jsr343-experts] Clebert Suconic's priorities
- [jsr343-experts] Collecting issues for JMS 2.next?
- [jsr343-experts] common connection factory instantiation
- [jsr343-experts] devoxx 2013
- [jsr343-experts] Discussion point: deadlocks in MessageListener and ExceptionListener
- [jsr343-experts] Draft JMS 2.0 javadocs can now be browsed online
- [jsr343-experts] Final editorial changes in the JMS 2.0 spec
- [jsr343-experts] For information: JSR-322 is starting
- [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] Java EE 7 roadmap
- [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] Java EE 8 Community Survey (results and next phase)
- [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] proposed MDB improvements
- [jsr343-experts] Fwd: [jsr342-experts] Java EE 8 features survey
- [jsr343-experts] Fwd: backwards compatibility requirements
- [jsr343-experts] General suggestions from Florian Beaufumé
- [jsr343-experts] Guidelines on backwards compatibility
- [jsr343-experts] Inconsistence on Javadoc regarding XAQueueConnection and XAConnection
- [jsr343-experts] Individual Client ACK
- [jsr343-experts] Interesting CDI issue
- [jsr343-experts] Is anyone interested in writing about JMS 2.0?
- [jsr343-experts] Java One BOF?
- [jsr343-experts] JavaOne 2012: What's New in Java Message Service 2.0 - Video now available
- [jsr343-experts] JavaOne 2014: JMS BOF and "meet the spec lead"
- [jsr343-experts] JMS 2 Plain Utility API Proposal
- [jsr343-experts] JMS 2.0 at JavaOne
- [jsr343-experts] JMS 2.0 Early Draft is posted
- [jsr343-experts] JMS 2.0 Early Draft ready for final review
- [jsr343-experts] JMS 2.0 Event Messaging
- [jsr343-experts] JMS 2.0 final approval ballot is approved
- [jsr343-experts] JMS 2.0 final release has now been submitted
- [jsr343-experts] JMS 2.0 final submission is this week
- [jsr343-experts] JMS 2.0 is now released!
- [jsr343-experts] JMS 2.0 late change: Activation property subscriptionScope
- [jsr343-experts] JMS 2.0 Late update: JMSProducer.getPropertyNames()
- [jsr343-experts] JMS 2.0 PR: Feedback from Goldman Sachs
- [jsr343-experts] JMS 2.0 Priorities for John Ament
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Adrian Johnson and Shivajee Samdarshi (TIBCO Software Inc.)
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Emran Shaik
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Julien Dubois
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Masoud Kalali
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Nigel Deakin
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Reza Rahman
- [jsr343-experts] JMS 2.0 Priorities: Proposal from Tom Barnes
- [jsr343-experts] JMS 2.0 Proposed final draft is now submitted
- [jsr343-experts] JMS 2.0 Proposed final draft is published
- [jsr343-experts] JMS 2.0 Public Draft - release candidate 1 is now ready for review
- [jsr343-experts] JMS 2.0 Public Draft is now published
- [jsr343-experts] JMS 2.0 Public draft review now complete
- [jsr343-experts] JMS 2.0 Public Review Ballot complete
- [jsr343-experts] JMS 2.0 Specification Document - Reorganisation
- [jsr343-experts] JMS 2.0: Planning the next stage
- [jsr343-experts] JMS 2.0: Progress so far
- [jsr343-experts] JMS 2.1 (JSR 368) expert group
- [jsr343-experts] JMS 2.1 Draft JSR
- [jsr343-experts] JMS at JavaOne
- [jsr343-experts] JMS at JavaOne San Francisco
- [jsr343-experts] JMS at JavaOne San Francisco 2012
- [jsr343-experts] JMS Object Scopes
- [jsr343-experts] JMS resource configuration in Java EE
- [jsr343-experts] JMS spec on Twitter
- [jsr343-experts] JMS Support for DI
- [jsr343-experts] JSR 343 has moved to JCP 2.9
- [jsr343-experts] JSR 343: Getting started
- [jsr343-experts] JSR 343: Summary of priorities so far
- [jsr343-experts] JSR 343: Transition to JCP 2.8
- [jsr343-experts] jsr343-experts mailing list
- [jsr343-experts] Late change: A.2.1 Simplified API: Injecting a JMSContext
- [jsr343-experts] Late change: A.3.1 Delivery delay (Issue 1: relationship to topic subscriptions)
- [jsr343-experts] Late change: A.3.1 Delivery delay (Issue 2: behaviour of QueueBrowser)
- [jsr343-experts] Late change: A.3.2 Meaning of noLocal with shared topic subscriptions
- [jsr343-experts] Late change: Drop maxIdleTime from <jms-connection-factory> and JMSConnectionFactoryDefinition
- [jsr343-experts] Late issue: Calling MessageConsumer#close from onMessage
- [jsr343-experts] Make Connection, Session and other interfaces implement AutoCodeable
- [jsr343-experts] Message-API
- [jsr343-experts] Message.setPriority versus Producer.setPriority
- [jsr343-experts] MessageApi proposal
- [jsr343-experts] OTN articles: What's New in JMS 2.0
- [jsr343-experts] Priorities for Graham Wallis
- [jsr343-experts] Proposals for MDB and RA standardisation (JMS_SPEC-30,55,54,25,73)
- [jsr343-experts] Proposed BOF at JavaOne
- [jsr343-experts] QueueBrowser.getEnumeration
- [jsr343-experts] Revised schedule for JSR 343
- [jsr343-experts] Session.createQueue / createTopoic
- [jsr343-experts] Slides from Devoxx 2011
- [jsr343-experts] State of a message in a producer after send
- [jsr343-experts] TCK Issue - com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client.msgPropertiesTest
- [jsr343-experts] TCK test that the transacted and acknowledge mode parameters are ignored
- [jsr343-experts] Updated JMS 2.0 spec schedule
- [jsr343-experts] Welcome Andrew Kennedy
- [jsr343-experts] Welcome John Archibold
- [jsr343-experts] Welcome John Harby
- [jsr343-experts] Welcome Matthew White
- [jsr343-experts] Welcome Nick Wright
- [jsr343-experts] Welcome Pravesh Pandya
- [jsr343-experts] Welcome Rob Davies
- [jsr343-experts] Welcome Sastry Malladi!
- [jsr343-experts] Where next for JMS?
- [jsr343-experts] Why are Destinations resources and not Strings?
- [jsr343-experts] {JMS_SPEC-30} Define mandatory activation config properties for JMS MDBs
- Batch Messages really abandoned?
- Batch processing...
- CDI Support in JMS 2.0
- Clarification about JMSContext and setClientID
- Clarification on JMSContext::createConsumer
- Collecting issues for JMS 2.next?
- Discussion point: deadlocks in MessageListener and ExceptionListener
- Draft JMS 2.0 javadocs can now be browsed online
- Feedback from JavaOne talk
- General suggestions from Florian Beaufumé
- Guidelines on backwards compatibility
- Inconsistence on Javadoc regarding XAQueueConnection and XAConnection
- Individual Client ACK
- Java One BOF?
- JMS 2 Plain Utility API Proposal
- JMS 2.0 at JavaOne
- JMS 2.0 Early Draft is posted
- JMS 2.0 Early Draft ready for final review
- JMS 2.0 Event Messaging
- JMS 2.0 Event Messaging (again!)
- JMS 2.0 is now released!
- JMS 2.0 late change: Activation property subscriptionScope
- JMS 2.0 Late update: JMSProducer.getPropertyNames()
- JMS 2.0 PR: Feedback from Goldman Sachs
- JMS 2.0 Priorities for John Ament
- JMS 2.0 Priorities: Proposal from Adrian Johnson and Shivajee Samdarshi (TIBCO Software Inc.)
- JMS 2.0 Priorities: Proposal from Emran Shaik
- JMS 2.0 Priorities: Proposal from Julien Dubois
- JMS 2.0 Public Draft - release candidate 1 is now ready for review
- JMS 2.0 Public Draft is now published
- JMS 2.0: Planning the next stage
- JMS 2.1 Draft JSR
- JMS at JavaOne San Francisco
- JMS at JavaOne San Francisco 2012
- JMS Object Scopes
- JMS over CDI or something else?
- JMS Support for DI
- JMS_SPEC-89: Standard API to create and configure a ConnectionFactory
- JMSProducer#getProperyNames()
- JSR 343: Getting started
- Late change: A.2.1 Simplified API: Injecting a JMSContext
- Late change: A.3.1 Delivery delay (Issue 1: relationship to topic subscriptions)
- Late change: A.3.1 Delivery delay (Issue 2: behaviour of QueueBrowser)
- Late change: A.3.2 Meaning of noLocal with shared topic subscriptions
- Late change: Drop maxIdleTime from <jms-connection-factory> and JMSConnectionFactoryDefinition
- Late issue: Calling MessageConsumer#close from onMessage
- Make Connection, Session and other interfaces implement AutoCodeable
- Make TemporaryQueue/Topic AutoCloseable?
- Message-API
- Poison Message Handling
- Proposals for MDB and RA standardisation (JMS_SPEC-30,55,54,25,73)
- Proposed BOF at JavaOne
- QueueBrowser.getEnumeration
- Session.createQueue / createTopoic
- Slides from Devoxx 2011
- TCK Issue - com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client.msgPropertiesTest
- TCK test that the transacted and acknowledge mode parameters are ignored
- Why are Destinations resources and not Strings?
- {JMS_SPEC-30} Define mandatory activation config properties for JMS MDBs
- Last message date: Tue Oct 20 17:12:16 2015
- Archived on: Thu Aug 10 15:14:55 2017 PDT