[jsr345-experts] Re: Clarifying requirements for the embeddable EJB container
I can add it too.
thanks,
-marina
David Blevins wrote:
> How about this for wording.
>
> "The embeddable API is designed to support the execution of EJB applications within a Java SE environment only. Use of the javax.ejb.embeddable package is not allowed from an application running in a JavaEE environment."
>
>
> -David
>
> On Apr 13, 2012, at 11:01 AM, David Blevins wrote:
>
>
>> On Apr 11, 2012, at 4:21 PM, Marina Vatkina wrote:
>>
>>
>>> Experts,
>>>
>>> Embeddable EJB container is intended to be used in a Java SE environment
>>> (only). It would be a stretch to require e.g. a Java EE PaaS provider to support bootstrapping of the EJB Container in a Java SE environment.
>>>
>> I've seen confusion from people thinking that the Embeddable EJBContainer API can be used inside an Application running in an EE platform (such as a webapp in Tomcat). Clarifying that would be great.
>>
>>
>>> Other technologies withing Java EE platform that provide support for a set of features withing Java SE environment do not require their vendors to do so. To follow this approach, I plan to make the following changes to the EJB 3.2 Core document:
>>>
>>> 1. Remove the section 'MISC', the row 'Embeddable API' and 'Note C' from
>>> the table 19 (p 406-407 EJB 3.2 Core) that list embeddable API as the
>>> set of required features in the EJB 3.2 container.
>>>
>> Note C was there to stress that the Embedded EJBContainer at minimum must support EJB Lite but vendors are allowed to support more. Some explicit note in the spec to state that would be great.
>>
>>
>>> 2. Replace the first sentence of the intro paragraph in Chapter 17 with the following:
>>>
>>> "The embeddable API is designed to support the execution of EJB applications within a Java SE environment."
>>>
>>> 3. Add the following as a second paragraph to the same section:
>>>
>>> "Support for the embeddable API is not required. However, any product
>>> that supports the embeddable API must adhere to the requirements of this specification."
>>>
>> This part I'm confused about. It sounds like the entire feature is being made optional which is how we deprecate things.
>>
>> Definitely we don't want that -- all vendors should be required to have support for the Embeddable EJBContainer API to be certified.
>>
>>
>> -David
>>
>>
>
>