users@jms-spec.java.net: by date

Friday, 2 March 2012
- [jms-spec users] [jsr343-experts] (JMS_SPEC-6) Add Reference to SOAP Binding Nigel Deakin
- [jms-spec users] [jsr343-experts] (JMS_SPEC-7) Provide HTTP Binding Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-6) Add Reference to SOAP Binding John D. Ament
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-6) Add Reference to SOAP Binding Reza Rahman
Sunday, 4 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding Sastry Malladi
Monday, 5 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding Nigel Deakin
- [jms-spec users] [jsr343-experts] (JMS_SPEC-9) Support for AMQP messaging Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding John D. Ament
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft ready for final review John D. Ament
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding Sastry Malladi
Tuesday, 6 March 2012
- [jms-spec users] [jsr343-experts] Revised schedule for JSR 343 Nigel Deakin
- [jms-spec users] Re: [jsr343-experts] Re: JMS 2.0 Early Draft ready for final review Pete Muir
Wednesday, 7 March 2012
- [jms-spec users] [jsr343-experts] Re: Re: Re: JMS 2.0 Early Draft ready for final review Nigel Deakin
- [jms-spec users] Re: [jsr343-experts] Re: Re: Re: JMS 2.0 Early Draft ready for final review Pete Muir
Thursday, 8 March 2012
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
Friday, 9 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-67) Relaxing the requirement to throw an exception if a message is sent to a deleted temp destination Nigel Deakin
Monday, 12 March 2012
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft is posted Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft is posted Nigel Deakin
- [jms-spec users] [jsr343-experts] JMS 2.0: Planning the next stage Nigel Deakin
Tuesday, 13 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Rob Davies
Thursday, 15 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Reza Rahman
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches John D. Ament
Friday, 16 March 2012
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft is posted Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches John Harby
Monday, 19 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-6) Add Reference to SOAP Binding Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Reza Rahman
Tuesday, 20 March 2012
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-36) Allow messages to be delivered asynchronously in batches Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Re: Re: JMS 2.0 Early Draft ready for final review Reza Rahman
- [jms-spec users] [jsr343-experts] Re: Re: Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: Re: JMS 2.0 Early Draft ready for final review Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Nigel Deakin
Wednesday, 21 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Re: JMS 2.0 Early Draft ready for final review Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Why are Destinations resources and not Strings? Rüdiger zu Dohna
Thursday, 22 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Why are Destinations resources and not Strings? Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Why are Destinations resources and not Strings? Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: Why are Destinations resources and not Strings? Nigel Deakin
Friday, 23 March 2012
- [jms-spec users] [jsr343-experts] Re: Why are Destinations resources and not Strings? Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-63) Introduce concept of platform default JMS connection factory in Java EE Nigel Deakin
Saturday, 24 March 2012
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage John D. Ament
Monday, 26 March 2012
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Rüdiger zu Dohna
Tuesday, 27 March 2012
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-46) Define standard API to create and configure a ConnectionFactory Nigel Deakin
- [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 Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container John D. Ament
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Why are Destinations resources and not Strings? Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container John D. Ament
- [jms-spec users] [jsr343-experts] (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way John D. Ament
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container John D. Ament
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way Rüdiger zu Dohna
Wednesday, 28 March 2012
- [jms-spec users] [jsr343-experts] JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-7) Provide HTTP Binding Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage John D. Ament
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage John Harby
Thursday, 29 March 2012
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage John D. Ament
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: JMS 2.0: Planning the next stage Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Poison Message Handling Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Poison Message Handling Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces John D. Ament
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API reza_rahman_at_lycos.com
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API John Harby
Friday, 30 March 2012
- [jms-spec users] [jsr343-experts] Re: [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces Rüdiger zu Dohna
- [jms-spec users] [jsr343-experts] Re: [jms-spec issues] (JMS_SPEC-88) Bind JMS to CDI events and/or business interfaces Nigel Deakin
- [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? Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-90) Provide simpler mechanism to refer to queues and topics in a portable way Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: (JMS_SPEC-64) Define simplified JMS API Nigel Deakin
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-7) Provide HTTP Binding Sastry Malladi
- [jms-spec users] [jsr343-experts] Re: Re: (JMS_SPEC-89) Define standard API to create and configure a ConnectionFactory in Java SE applications and by a Java EE container Reza Rahman

Last message date: Fri Mar 30 08:31:17 2012
Archived on: Thu Aug 10 15:15:03 2017 PDT

101 messages sort by: [ thread ] [ author ] [ date ] [ subject ] [ attachment ]
Other periods:[ Previous, Date view ] [ Next, Date view ] [ List of Folders ]
Nearby: [ About this archive ] [ Other mail archives ]