Carlo de Wolf wrote:
> 4.4.1.2 java:module
> Note that the existence of global JNDI names for the local and
> no-interface client views does not imply
> that cross-application access to those entries is required. See
> Section 3.2.2 for more details. [XXX ???]
>
> Is actually a foot-note to 4.4.1 Syntax. Which shows that the chapter
> is weirdly structured. It should be a section in some
> java:global chapter.
4.4 is the "Global JNDI Access". Should I just move it to bottom of
4.4.1 to make it clear?
thanks,
-marina
>
> Carlo
>
> On 07/06/2011 01:02 AM, Marina Vatkina wrote:
>> Dear Experts,
>>
>> Before we go any further on the discussions of the spec improvements,
>> we need to close on several issues with the current version:
>>
>> 1. Vote on the optionality of the Entity Beans and JAX-RPC based Web
>> Service Endpoints (and the split of the spec into 2 parts, but the
>> split is the secondary issue). I have only 3 votes (positive) so far.
>>
>> 2. Close on the items marked by Linda as XXX in the drafts.
>>
>> 3. Define *deterministic* rules in the EJB spec about EJB Lite vs.
>> EJB Full list of features in regards to the EJB support in a Web
>> Profile container. In addition to be very flexible (contrary to the
>> regular Java EE approach, and the expectations of the EJB TCK), the
>> current wording in the spec does not make it clear a) what is
>> expected and what is not in the Web Profile, and b) if we keep it
>> flexible, how a user (at deployment and/or runtime) can determine if
>> a specific feature outside EJB Lite is available/supported.
>>
>> The same applies to the Embeddable EJB Container.
>>
>> Thank you,
>> -marina
>>
>>
>