- (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-144) StreamMessage#getBody(Class<T>)
- (JMS_SPEC-25) Standardise the interface between a JMS provider and a Java EE application server
- (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-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 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-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
- [ejb-spec users] [jsr345-experts] JMS 2.0 session creation in MDB lifecycle callback
- [javaee-spec users] [jsr366-experts] Organizing CDI workshop for Java EE specs during Java One
- [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jms-spec users]
- [jms-spec users] [jsr343-experts] (JMS_SPEC-101) New method Message.getPayload(Class<T> c)
- [jms-spec users] [jsr343-experts] (JMS_SPEC-102) Make JMSConsumer.receivePayload methods consistent with Message.getBody
- [jms-spec users] [jsr343-experts] (JMS_SPEC-105) Provide API to allow an app server or resource adapter to obtain a XAResource from a JMSContext
- [jms-spec users] [jsr343-experts] (JMS_SPEC-106) Methods on JMSContext that are disallowed if the context is injected should throw a IllegalStateException not a JMSException
- [jms-spec users] [jsr343-experts] (JMS_SPEC-107) Extend connection consumer API to support shared durable and non-durable subscriptions
- [jms-spec users] [jsr343-experts] (JMS_SPEC-108) add generics to methods currently returning raw types
- [jms-spec users] [jsr343-experts] (JMS_SPEC-109) add method Destination.getName()
- [jms-spec users] [jsr343-experts] (JMS_SPEC-112) add Message.getJMSDeliveryCount()
- [jms-spec users] [jsr343-experts] (JMS_SPEC-115) Remove the statement that portable applications should only have one consumer per queue
- [jms-spec users] [jsr343-experts] (JMS_SPEC-116) Take advantage of EJB 3.2's RA improvement for MDBs
- [jms-spec users] [jsr343-experts] (JMS_SPEC-119) Remove reference to password alias
- [jms-spec users] [jsr343-experts] (JMS_SPEC-121) Injection of JMSContext objects not possible in a WebSocket @OnMessage or @OnClose callback method
- [jms-spec users] [jsr343-experts] (JMS_SPEC-27) Clarify the relationship between the JMS and other Java EE specifications
- [jms-spec users] [jsr343-experts] (JMS_SPEC-4) Properties on Messages should follow builder pattern.
- [jms-spec users] [jsr343-experts] (JMS_SPEC-6) Add Reference to SOAP Binding
- [jms-spec users] [jsr343-experts] (JMS_SPEC-61) Selector on JMS body
- [jms-spec users] [jsr343-experts] (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE
- [jms-spec users] [jsr343-experts] (JMS_SPEC-64) Define simplified JMS API
- [jms-spec users] [jsr343-experts] (JMS_SPEC-65) Clarify use of NoLocal arg when using createDurableSubscriber
- [jms-spec users] [jsr343-experts] (JMS_SPEC-67) Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- [jms-spec users] [jsr343-experts] (JMS_SPEC-68) Add new method Session.acknowledge()
- [jms-spec users] [jsr343-experts] (JMS_SPEC-69) Clarify that QueueRequestor and TopicRequestor only work in a non-transacted session with auto or dups-ok ack
- [jms-spec users] [jsr343-experts] (JMS_SPEC-7) Provide HTTP Binding
- [jms-spec users] [jsr343-experts] (JMS_SPEC-70) Define annotations for injecting MessagingContext objects
- [jms-spec users] [jsr343-experts] (JMS_SPEC-73) Define how messages from a topic are delivered to clustered application server instances
- [jms-spec users] [jsr343-experts] (JMS_SPEC-77) MapMessage.setBytes API discrepancy found in the javadocs
- [jms-spec users] [jsr343-experts] (JMS_SPEC-80) Error in example 9.3.3.2 "Reconnect to a topic using a durable subscription"
- [jms-spec users] [jsr343-experts] (JMS_SPEC-86) Chapter 1 "Introduction" is a little dated and requires rewriting
- [jms-spec users] [jsr343-experts] (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container
- [jms-spec users] [jsr343-experts] (JMS_SPEC-9) Support for AMQP messaging
- [jms-spec users] [jsr343-experts] (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way
- [jms-spec users] [jsr343-experts] (JMS_SPEC-93) Does changing the noLocal flag when connecting to a durable subscription cause the durable subscription to be deleted?
- [jms-spec users] [jsr343-experts] (JMS_SPEC-94) Define what characters are valid in a durable (or shared subscription) name
- [jms-spec users] [jsr343-experts] (JMS_SPEC-96 & 97) Define Java EE connection factory and destination definition annotations and descriptor elements
- [jms-spec users] [jsr343-experts] (JMS_SPEC-98) Fix findbugs warnings in JMSException, JMSRuntimeException, QueueRequestor, TopicRequestor
- [jms-spec users] [jsr343-experts] [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces
- [jms-spec users] [jsr343-experts] AUTO: Matthew White/UK/IBM is out of the office (returning 20/02/2013)
- [jms-spec users] [jsr343-experts] AUTO: Matthew White/UK/IBM is out of the office sick (returning 28/01/2013)
- [jms-spec users] [jsr343-experts] AUTO: Matthew White/UK/IBM is out of the office until 13th August 2012 (returning 13/08/2012)
- [jms-spec users] [jsr343-experts] AUTO: Matthew White/UK/IBM is out of the office until 3rd January (returning 02/01/2013)
- [jms-spec users] [jsr343-experts] Batch Messages really abandoned?
- [jms-spec users] [jsr343-experts] Can I start work on JMS 2.1 spec changes for the ACK mode related issues?
- [jms-spec users] [jsr343-experts] Clarification about JMSContext and setClientID
- [jms-spec users] [jsr343-experts] Clarification on JMSContext::createConsumer
- [jms-spec users] [jsr343-experts] Collecting issues for JMS 2.next?
- [jms-spec users] [jsr343-experts] common connection factory instantiation
- [jms-spec users] [jsr343-experts] devoxx 2013
- [jms-spec users] [jsr343-experts] Draft JMS 2.0 javadocs can now be browsed online
- [jms-spec users] [jsr343-experts] Final editorial changes in the JMS 2.0 spec
- [jms-spec users] [jsr343-experts] For information: JSR-322 is starting
- [jms-spec users] [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] Java EE 7 roadmap
- [jms-spec users] [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] Java EE 8 Community Survey (results and next phase)
- [jms-spec users] [jsr343-experts] Fwd: [javaee-spec users] [jsr342-experts] proposed MDB improvements
- [jms-spec users] [jsr343-experts] Fwd: [jsr342-experts] Java EE 8 features survey
- [jms-spec users] [jsr343-experts] General suggestions from Florian Beaufumé
- [jms-spec users] [jsr343-experts] Inconsistence on Javadoc regarding XAQueueConnection and XAConnection
- [jms-spec users] [jsr343-experts] Individual Client ACK
- [jms-spec users] [jsr343-experts] Is anyone interested in writing about JMS 2.0?
- [jms-spec users] [jsr343-experts] Java One BOF?
- [jms-spec users] [jsr343-experts] JavaOne 2012: What's New in Java Message Service 2.0 - Video now available
- [jms-spec users] [jsr343-experts] JavaOne 2014: JMS BOF and "meet the spec lead"
- [jms-spec users] [jsr343-experts] JMS 2.0 Early Draft is posted
- [jms-spec users] [jsr343-experts] JMS 2.0 Early Draft ready for final review
- [jms-spec users] [jsr343-experts] JMS 2.0 final approval ballot is approved
- [jms-spec users] [jsr343-experts] JMS 2.0 final release has now been submitted
- [jms-spec users] [jsr343-experts] JMS 2.0 final submission is this week
- [jms-spec users] [jsr343-experts] JMS 2.0 is now released!
- [jms-spec users] [jsr343-experts] JMS 2.0 late change: Activation property subscriptionScope
- [jms-spec users] [jsr343-experts] JMS 2.0 Late update: JMSProducer.getPropertyNames()
- [jms-spec users] [jsr343-experts] JMS 2.0 PR: Feedback from Goldman Sachs
- [jms-spec users] [jsr343-experts] JMS 2.0 Proposed final draft is now submitted
- [jms-spec users] [jsr343-experts] JMS 2.0 Proposed final draft is published
- [jms-spec users] [jsr343-experts] JMS 2.0 Public Draft - release candidate 1 is now ready for review
- [jms-spec users] [jsr343-experts] JMS 2.0 Public Draft is now published
- [jms-spec users] [jsr343-experts] JMS 2.0 Public draft review now complete
- [jms-spec users] [jsr343-experts] JMS 2.0 Public Review Ballot complete
- [jms-spec users] [jsr343-experts] JMS 2.0 Specification Document - Reorganisation
- [jms-spec users] [jsr343-experts] JMS 2.0: Planning the next stage
- [jms-spec users] [jsr343-experts] JMS 2.1 (JSR 368) expert group
- [jms-spec users] [jsr343-experts] JMS 2.1 Draft JSR
- [jms-spec users] [jsr343-experts] JMS at JavaOne
- [jms-spec users] [jsr343-experts] JMS at JavaOne San Francisco
- [jms-spec users] [jsr343-experts] JMS at JavaOne San Francisco 2012
- [jms-spec users] [jsr343-experts] JMS spec on Twitter
- [jms-spec users] [jsr343-experts] JSR 343 has moved to JCP 2.9
- [jms-spec users] [jsr343-experts] JSR 343: Transition to JCP 2.8
- [jms-spec users] [jsr343-experts] Late change: A.2.1 Simplified API: Injecting a JMSContext
- [jms-spec users] [jsr343-experts] Late change: A.3.1 Delivery delay (Issue 1: relationship to topic subscriptions)
- [jms-spec users] [jsr343-experts] Late change: A.3.1 Delivery delay (Issue 2: behaviour of QueueBrowser)
- [jms-spec users] [jsr343-experts] Late change: A.3.2 Meaning of noLocal with shared topic subscriptions
- [jms-spec users] [jsr343-experts] Late change: Drop maxIdleTime from <jms-connection-factory> and JMSConnectionFactoryDefinition
- [jms-spec users] [jsr343-experts] Late issue: Calling MessageConsumer#close from onMessage
- [jms-spec users] [jsr343-experts] OTN articles: What's New in JMS 2.0
- [jms-spec users] [jsr343-experts] Proposals for MDB and RA standardisation (JMS_SPEC-30,55,54,25,73)
- [jms-spec users] [jsr343-experts] QueueBrowser.getEnumeration
- [jms-spec users] [jsr343-experts] Revised schedule for JSR 343
- [jms-spec users] [jsr343-experts] State of a message in a producer after send
- [jms-spec users] [jsr343-experts] TCK Issue - com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client.msgPropertiesTest
- [jms-spec users] [jsr343-experts] TCK test that the transacted and acknowledge mode parameters are ignored
- [jms-spec users] [jsr343-experts] Updated JMS 2.0 spec schedule
- [jms-spec users] [jsr343-experts] Welcome Andrew Kennedy
- [jms-spec users] [jsr343-experts] Welcome John Archibold
- [jms-spec users] [jsr343-experts] Welcome John Harby
- [jms-spec users] [jsr343-experts] Welcome Matthew White
- [jms-spec users] [jsr343-experts] Welcome Nick Wright
- [jms-spec users] [jsr343-experts] Welcome Pravesh Pandya
- [jms-spec users] [jsr343-experts] Welcome Rob Davies
- [jms-spec users] [jsr343-experts] Welcome Sastry Malladi!
- [jms-spec users] [jsr343-experts] Where next for JMS?
- [jms-spec users] [jsr343-experts] Why are Destinations resources and not Strings?
- [jms-spec users] [jsr368-experts] Advice: mirror on GitHub
- [jms-spec users] [jsr368-experts] createContext on Queue and Topic Connection Factories
- [jms-spec users] [jsr368-experts] Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan
- [jms-spec users] [jsr368-experts] JavaOne 2016
- [jms-spec users] [jsr368-experts] JMS 2.0 errata is now released
- [jms-spec users] [jsr368-experts] JMS 2.0 errata now available for formal review
- [jms-spec users] [jsr368-experts] JMS 2.0 errata: final request for comments
- [jms-spec users] [jsr368-experts] JMS 2.0 errata: JMS_SPEC-125 (Define whether a JMS provider should call reset after sending a BytesMessage asynchronously)
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-157 (JMS 2.0 introduced an incompatible restriction on creating two sessions per connection in Java EE)
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-160 (JMS API source contains self-closing HTML tags)
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-161 (serialVersionUID of JMSException has changed from JMS 1.1 to JMS 2.0 )
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-162 (Typos in section 7.3 "Asynchronous send")
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-163 (Javadoc for JMSContext#setClientID contains obsolete MessageContext reference)
- [jms-spec users] [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-167: Session javadoc should mention consumer.close is allowed outside thread of control
- [jms-spec users] [jsr368-experts] JMS 2.0 errata: MS_SPEC-164 (Typos in section 7.3.5 and 12.2: Change Session to MessageProducer)
- [jms-spec users] [jsr368-experts] JMS 2.0 errata: Summary of proposed changes
- [jms-spec users] [jsr368-experts] JMS_SPEC-133: Update javadoc comments for QueueConnection#createQueueSession and TopicConnection#createTopicSession
- [jms-spec users] [jsr368-experts] JMS_SPEC-155 (JMS 2.0 introduced incompatible changes to createSession(bool,int))
- [jms-spec users] [jsr368-experts] JMS_SPEC-165: Error in javadoc for Connection#stop and JMSContext#stop
- [jms-spec users] [jsr368-experts] JMS_SPEC-166: Define that the JMS provider should call reset on a StreamMessage passed to a CompletionListener
- [jms-spec users] [jsr368-experts] svn -> git (GitHub)
- [jms-spec users] About JMS_SPEC-116
- [jms-spec users] Adopt a JSR JMS 2.0 Workshop in London
- [jms-spec users] AUTO: Matthew White/UK/IBM is out of the office (returning 20/02/2013)
- [jms-spec users] AUTO: Matthew White/UK/IBM is out of the office until 3rd January (returning 02/01/2013)
- [jms-spec users] Confusion about JMSProducer methods and CDI
- [jms-spec users] FasoJUG join effort of "Adopt JSR #343"
- [jms-spec users] Future of JMS Spec with Java.net closing?
- [jms-spec users] Issue I18: Legacy MessageListener and _at_JMSListener compatibility
- [jms-spec users] java.net.jms-spec has been migrated to GitHub and groups.io discussion service
- [jms-spec users] JavaOne
- [jms-spec users] JavaOne 2015: Come to the GlassFish - NetBeans - Payara Party
- [jms-spec users] JavaOne presentation: what's (probably) coming in JMS 2.1
- [jms-spec users] JavaOne San Francisco 2015
- [jms-spec users] JMS 2.0 errata
- [jms-spec users] JMS 2.0 Errata: JMS_SPEC-158 (JMS 2.0 introduced incompatible changes to Connection.stop and close and Session.close)
- [jms-spec users] JMS 2.0: enhancement request: more flexible acknowledgment modes
- [jms-spec users] JMS 2.0: question about scope of shared non-durable and durable subscriptions
- [jms-spec users] JMS 2.1 Early Draft 1 is posted
- [jms-spec users] JMS 2.1 expert group and community meeting to discuss flexible JMS MDBs
- [jms-spec users] JMS 2.1 Ideas
- [jms-spec users] JMS 2.1 plan
- [jms-spec users] JMS 2.1 schedule update
- [jms-spec users] JMS over CDI or something else?
- [jms-spec users] JMS Topics and historical data
- [jms-spec users] JMS2.0 javadocs
- [jms-spec users] jms2.0 spec adoption into glassfish
- [jms-spec users] JMS20Demo app on diff configurations
- [jms-spec users] JMS_SPEC-116: JMS MDB improvements:
- [jms-spec users] JMS_SPEC-116: JMS MDB improvements: simplifying the annotations
- [jms-spec users] JMS_SPEC-116: Make Message Poisoning Handling a priority?
- [jms-spec users] JMS_SPEC-116: Take advantage of EJB 3.2's RA improvement for MDBs
- [jms-spec users] JMS_SPEC-134: Declarative Annotation Based JMS Listeners
- [jms-spec users] JMS_SPEC-172: Make it easier to find JMS Resources
- [jms-spec users] JMS_SPEC-36: Batch delivery
- [jms-spec users] JMSConnectionFactoryDefinition in spec?
- [jms-spec users] JMSException#getCause()
- [jms-spec users] JMSProducer#getProperyNames()
- [jms-spec users] JSR 368 (JMS 2.1) has been approved
- [jms-spec users] JSR 368 (JMS 2.1) is now submitted and open for formal review
- [jms-spec users] Make TemporaryQueue/Topic AutoCloseable?
- [jms-spec users] Message Observers
- [jms-spec users] MessageListener::onMessage Replacement?
- [jms-spec users] Minutes of JMS 2.1 Meeting 19 Oct 2015
- [jms-spec users] Minutes of JMS 2.1 Meeting 2 on 12 Nov 2015
- [jms-spec users] Minutes of JMS 2.1 Meeting 3 on 19 Nov 2014
- [jms-spec users] Observer
- [jms-spec users] PoolSize Configuration
- [jms-spec users] Posting to this list (users_at_jms-spec.java.net)
- [jms-spec users] Proposal to release Early Draft 1
- [jms-spec users] Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- [jms-spec users] Security alignment of JMS
- [jms-spec users] Sending a previously-received Message and supporting JMSXUserID
- [jms-spec users] StreamMessage#getBody(Class<T>)
- [jms-spec users] The future of JMS 2.1 and Java EE 8
- [jms-spec users] Welcome new expert group member: Ivar Grimstad
- [jms-spec users] Welcome to the jsr368-experts_at_jms-spec.java.net mailing list!
- [jms-spec users] What is the expected value returned by setClientID when client identifier is unset?
- [jsr343-experts] (JMS_SPEC-102) Make JMSConsumer.receivePayload methods consistent with Message.getBody
- [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] Interesting CDI issue
- [jsr343-experts] Late change: A.3.1 Delivery delay (Issue 1: relationship to topic subscriptions)
- [jsr343-experts] Late change: A.3.2 Meaning of noLocal with shared topic subscriptions
- [jsr345-experts] Fwd: [jsr342-experts] proposed MDB improvements
- [jsr366-experts] Organizing CDI workshop for Java EE specs during Java One
- [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-161 (serialVersionUID of JMSException has changed from JMS 1.1 to JMS 2.0 )
- About JMS_SPEC-116
- Adopt a JSR JMS 2.0 Workshop in London
- Advice: mirror on GitHub
- Batch Messages really abandoned?
- Clarification about JMSContext and setClientID
- Clarification on JMSContext::createConsumer
- Collecting issues for JMS 2.next?
- Confusion about JMSProducer methods and CDI
- createContext on Queue and Topic Connection Factories
- Digest for list users_at_jms-spec.java.net
- Draft JMS 2.0 javadocs can now be browsed online
- Face-to-face meeting at JavaOne
- FasoJUG join effort of "Adopt JSR #343"
- Feedback from JavaOne talk
- Future of JMS Spec with Java.net closing?
- Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan
- General suggestions from Florian Beaufumé
- Improvements for JMS MDBs
- Inconsistence on Javadoc regarding XAQueueConnection and XAConnection
- Individual Client ACK
- Issue I18: Legacy MessageListener and @JMSListener compatibility
- Java One BOF?
- java.net.jms-spec has been migrated to GitHub and groups.io discussion service
- JavaOne
- JavaOne 2016
- JavaOne presentation: what's (probably) coming in JMS 2.1
- JavaOne San Francisco 2015
- JMS 2.0 Early Draft is posted
- JMS 2.0 Early Draft ready for final review
- JMS 2.0 errata now available for formal review
- JMS 2.0 errata: final request for comments
- JMS 2.0 errata: JMS_SPEC-125 (Define whether a JMS provider should call reset after sending a BytesMessage asynchronously)
- JMS 2.0 Errata: JMS_SPEC-157 (JMS 2.0 introduced an incompatible restriction on creating two sessions per connection in Java EE)
- JMS 2.0 Errata: JMS_SPEC-158 (JMS 2.0 introduced incompatible changes to Connection.stop and close and Session.close)
- JMS 2.0 Errata: JMS_SPEC-161 (serialVersionUID of JMSException has changed from JMS 1.1 to JMS 2.0 )
- JMS 2.0 Errata: JMS_SPEC-167: Session javadoc should mention consumer.close is allowed outside thread of control
- JMS 2.0 errata: Summary of proposed changes
- 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: Proposal from Julien Dubois
- JMS 2.0 Priorities: Proposal from Rüdiger zu Dohna
- JMS 2.0 Public Draft - release candidate 1 is now ready for review
- JMS 2.0 Public Draft is now published
- JMS 2.0: enhancement request: more flexible acknowledgment modes
- JMS 2.0: Planning the next stage
- JMS 2.0: question about scope of shared non-durable and durable subscriptions
- JMS 2.1 (JSR 368) expert group
- JMS 2.1 Draft JSR
- JMS 2.1 expert group and community meeting to discuss flexible JMS MDBs
- JMS 2.1 Ideas
- JMS at JavaOne
- JMS at JavaOne San Francisco
- JMS at JavaOne San Francisco 2012
- JMS over CDI or something else?
- JMS Support for DI
- JMS Topics and historical data
- JMS2.0 javadocs
- jms2.0 spec adoption into glassfish
- JMS20Demo app on diff configurations
- JMS_SPEC-116: JMS MDB improvements:
- JMS_SPEC-116: JMS MDB improvements: simplifying the annotations
- JMS_SPEC-116: Make Message Poisoning Handling a priority?
- JMS_SPEC-116: Take advantage of EJB 3.2's RA improvement for MDBs
- JMS_SPEC-134: Declarative Annotation Based JMS Listeners
- JMS_SPEC-155 (JMS 2.0 introduced incompatible changes to createSession(bool,int))
- JMS_SPEC-165: Error in javadoc for Connection#stop and JMSContext#stop
- JMS_SPEC-172: Make it easier to find JMS Resources
- JMS_SPEC-36: Batch delivery
- JMS_SPEC-89: Standard API to create and configure a ConnectionFactory
- JMSConnectionFactoryDefinition in spec?
- JMSException#getCause()
- JMSProducer#getProperyNames()
- 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 Observers
- MessageListener::onMessage Replacement?
- Minutes of JMS 2.1 Meeting 19 Oct 2015
- Minutes of JMS 2.1 Meeting 2 on 12 Nov 2015
- Minutes of JMS 2.1 Meeting 3 on 19 Nov 2014
- Minutes of JMS 2.1 Meeting 3 on 19 Nov 2014)
- Observer
- Poison Message Handling
- PoolSize Configuration
- Proposal to release Early Draft 1
- Proposals for MDB and RA standardisation (JMS_SPEC-30,55,54,25,73)
- QueueBrowser.getEnumeration
- Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination
- Security alignment of JMS
- Sending a previously-received Message and supporting JMSXUserID
- Singleton MDB?
- Slides from Devoxx 2011
- State of a message in a producer after send
- svn -> git (GitHub)
- TCK Issue - com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client.msgPropertiesTest
- TCK test that the transacted and acknowledge mode parameters are ignored
- The future of JMS 2.1 and Java EE 8
- WebContainer API on Servlets
- Welcome new expert group member: Ivar Grimstad
- Welcome Rob Davies
- Welcome Sastry Malladi!
- What is the expected value returned by setClientID when client identifier is unset?
- Why are Destinations resources and not Strings?
- {JMS_SPEC-30} Define mandatory activation config properties for JMS MDBs
- Last message date: Thu May 11 19:39:00 2017
- Archived on: Thu Aug 10 15:15:03 2017 PDT