jsr343-experts@jms-spec.java.net

[jsr343-experts] Re: JMS 2.0: Planning the next stage

From: Nigel Deakin <nigel.deakin_at_oracle.com>
Date: Tue, 01 May 2012 15:24:19 +0100

Thanks to the four of you who who voted on what P3 issues we should discuss after we've completed the P2 list. This is
very helpful

Further votes welcome! I would like to invite everyone else from the EG to select up to *6* issues from the *22 *issues
listed in the two tables below that /you /think we should discuss. Anything not shortlisted will stay on the list for
later.

I've created a wiki page http://java.net/projects/jms-spec/pages/JSR343Planning which shows the votes so far.

Thanks,

Nigel

On 28/03/2012 15:13, Nigel Deakin wrote:
>
> *Priority 3: New Issues*
>
> We now come to the new issues which we have not formally considered yet. I think we should plan to discuss all of
> them, even if the conclusion is to do nothing. However, bearing in mind the Priority 2 issues above, I don't think we
> are going to have time to discuss all of them in time for JMS 2.0 so we decide which ones to discuss first:
>
> Here are the 14 larger new issues:
>
> JMS_SPEC-90 <http://java.net/jira/browse/JMS_SPEC-90> Provide simpler mechanism to refer to queues and topics in a
> portable way
> JMS_SPEC-88 <http://java.net/jira/browse/JMS_SPEC-88> Bind JMS to CDI events and/or business interfaces
> JMS_SPEC-83 <http://java.net/jira/browse/JMS_SPEC-83> Tighter specification of Expired Message Handling in Section
> 4.8 "Message Time-to-Live"
> JMS_SPEC-74 <http://java.net/jira/browse/JMS_SPEC-74> Define lifecycle of durable subscriptions used by MDBs
> JMS_SPEC-73 <http://java.net/jira/browse/JMS_SPEC-73> Define how messages from a topic are delivered to clustered
> application server instances
> JMS_SPEC-72 <http://java.net/jira/browse/JMS_SPEC-72> Poison message management
> JMS_SPEC-59 <http://java.net/jira/browse/JMS_SPEC-59> Basic metadata/management via JMS
> JMS_SPEC-58 <http://java.net/jira/browse/JMS_SPEC-58> New method Message.copyMessage() to create a mutable copy of a
> received message
> JMS_SPEC-37 <http://java.net/jira/browse/JMS_SPEC-37> Last Value Cache Feature for a topic.
> JMS_SPEC-21 <http://java.net/jira/browse/JMS_SPEC-21> Support for pre-acknowledge ack mode
> JMS_SPEC-18 <http://java.net/jira/browse/JMS_SPEC-18> Standard set of server JMX MBeans
> JMS_SPEC-14 <http://java.net/jira/browse/JMS_SPEC-14> Durable subscription browser
> JMS_SPEC-7 <http://java.net/jira/browse/JMS_SPEC-7> Provide HTTP Binding
> JMS_SPEC-5 <http://java.net/jira/browse/JMS_SPEC-5> Multi-Value Support in Properties
>
>
> Here are the 8 smaller new issues:
>
> JMS_SPEC-91 <http://java.net/jira/browse/JMS_SPEC-91> New "relaxed message order" option
> JMS_SPEC-79 <http://java.net/jira/browse/JMS_SPEC-79> New factory methods to create BytesMessage and MapMessage and
> set the payload
> JMS_SPEC-71 <http://java.net/jira/browse/JMS_SPEC-71> Change XAConnectionFactory to extend ConnectionFactory
> JMS_SPEC-68 <http://java.net/jira/browse/JMS_SPEC-68> Add new method Session.acknowledge()
> JMS_SPEC-67 <http://java.net/jira/browse/JMS_SPEC-67> Relaxing the requirement to throw an exception if a message is
> sent to a deleted temp destination
> JMS_SPEC-66 <http://java.net/jira/browse/JMS_SPEC-66> Define how MessageConsumer.receive should handle a thread
> interrupt
> JMS_SPEC-24 <http://java.net/jira/browse/JMS_SPEC-24> Clarify classloader used in ObjectMessage.getObject() and/or
> provide new method getObject(ClassLoader classLoader)
> JMS_SPEC-22 <http://java.net/jira/browse/JMS_SPEC-22> Add JMS defined property JMSXGroupLast
>
>
>
>