On 09/10/2011 12:34 AM, Marina Vatkina wrote:
> Carlo de Wolf wrote:
>> If it needs to move, it would actually make more sense to move it to
>> 3.4 Client View of Session Beans Written to the EJB 3.x Simplified API.
>>
>> Which actually highlights a little issue, we didn't specify anything
>> for EJB 2 view JNDI names.
>
> The spec says in 4.4.1
>
> "The container registers a separate JNDI name entry for each local
> business interface, each remote business interface, any no-interface
> view, any local home interface, and any remote home interface. For the
> no-interface view, the last portion of the entry name is the
> fully-qualified name of the bean class."
>
> Doesn't it cover 2.x?
Yup, my bad.
Carlo
>
> thanks,
> -marina
>>
>> Carlo
>>
>> On 09/08/2011 11:32 AM, Stefan Heldt wrote:
>>> Marina,
>>>
>>> I wouldn't move it to 16.3.2 as that section is quite general and
>>> section 4.4 is very specific to session beans. I don't see the need
>>> for relocation because section 4.4 describes the contract between
>>> session beans and the container regarding JNDI. So I vote for option
>>> c) do nothing ;-)
>>>
>>> Regards
>>> Stefan!
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Marina Vatkina [mailto:marina.vatkina_at_oracle.com]
>>> Gesendet: Mittwoch, 7. September 2011 22:48
>>> An: jsr345-experts_at_ejb-spec.java.net
>>> Betreff: [jsr345-experts] XXX Moving section 4.4?
>>>
>>> Experts,
>>>
>>> Section "4.4 Access in the Global JNDI Namespace" seems to have a
>>> more generic content than "Session Bean Component Contract" chapter
>>> where it is currently located (see also Linda's to-do list at the
>>> end of the spec).
>>>
>>> I can either
>>>
>>> a) move it under "16.3.2 JNDI Requirements" (Chapter 16 Runtime
>>> Environment)
>>> or
>>> b) create a separate chapter from it
>>>
>>> Please vote or suggest another option.
>>>
>>> thanks,
>>> -marina
>>