users@jms-spec.java.net

[jms-spec users] Re: [ejb-spec users] Re: [jsr345-experts] Fwd: [jsr342-experts] proposed MDB improvements

From: Nigel Deakin <nigel.deakin_at_oracle.com>
Date: Mon, 18 Mar 2013 10:17:34 +0000

Philippe,

On 18/03/2013 09:54, Philippe Marschall wrote:
>
>
> On 11.03.2013 05:36, Marina Vatkina wrote:
>> Philippe,
>>
>> On 3/10/13 7:56 AM, Philippe Marschall wrote:
>>>
>>>
>>> On 08.03.2013 20:22, Marina Vatkina wrote:
>>>> Experts,
>>>>
>>>> This is our chance at modernizing MDBs in the Java EE 7 release.
>>>
>>> We'll quite frankly I don't wee why massive changes like this one can
>>> make it in at such a late time but absolutely minor changes like
>>> making existing methods return generic instead of raw types and
>>> supporting Exception#getCause() have to wait at least for another four
>>> years.
>>
>> Were these requests ever filed in the ejb-spec JIRA? If they were not,
>> we didn't know about them. If they were and we missed them - sorry. An
>> API change is a tricky thing because what can be seen as a simple
>> change, might break an existing application (or cause unnecessary
>> warnings for that matter).
>>
>> That said, which Exception#getCause() do you have in mind? All EJB
>> exceptions inherit getCause from Throwable.
>
> [1], [2], OK different spec but very closely related [3] and same EE7 schedule.
>
> [1] http://java.net/jira/browse/JMS_SPEC-108
> [2] http://java.net/jira/browse/JMS_SPEC-113
> [3] http://java.net/jira/browse/JMS_SPEC-116

I don't understand what point you are making. Are you asking why there isn't enough time to add new features to JMS 2.0?

Nigel