jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: Low-level JAX-RS client API proposal

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Mon, 16 May 2011 22:05:01 +0200

On 05/14/2011 09:45 AM, Markus KARG wrote:
> If it can be removed in EE 7, it will be gone and will not run CMR anymore. So what is untrue here?

To clarify, the CMP/BMP feature was *pruned*, not deprecated[*]. Also, pruned features will *NOT* be removed from the
JavaEE spec, they will be made optional. IOW, JavaEE compliant implementations may choose not to implement an optional
feature without loosing the compliance status. However, RIs are expected to still keep supporting all the previously
pruned and now optional features.

Marek

>
>> -----Original Message-----
>> From: Bill Burke [mailto:bburke_at_redhat.com]
>> Sent: Freitag, 13. Mai 2011 23:46
>> To: jsr339-experts_at_jax-rs-spec.java.net
>> Subject: [jsr339-experts] Re: Low-level JAX-RS client API proposal
>>
>>
>>
>> On 5/13/11 2:18 PM, Markus KARG wrote:
>>> Nobody disallows it an EJB broke BW compatibility from EJB 2 to EJB
>> 3, too, and plans to drop even more legacy features in future. So why
>> should especially rather new JAX RS not be allowed to?
>>>
>>
>> Markus, this is *COMPLETELY* untrue. EJB 3 was BW compatible with
>> EJB2.
>> An EJB 2.x bean must be deployable in an EJB3 container. CMP/BMP was
>> deprecated in EE6, but required by compliant implementations of EE6.
>> After one major release marked for deprecation, it can be removed in EE
>> 7.
>>
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>