The EJB spec should be specifying the out-going part of EJB, while the
EE spec should aggregate all in-coming. Both ends must be a 100% fit.
The global JNDI name is a common attribute of both ends.
I think the EJB spec should be complete and concise, not be scattered
across multiple.
Carlo
On 09/12/2011 10:09 AM, Antonio Goncalves wrote:
> Shouldn't EE related topics be move to the EE spec ? The global JNDI
> access is broader than just EJBs, why not move this section under EE 5
> (Resources, Naming, and Injection) ?
>
> Antonio
>
> On Sat, Sep 10, 2011 at 00:32, Marina Vatkina
> <marina.vatkina_at_oracle.com <mailto:marina.vatkina_at_oracle.com>> wrote:
>
> I have the following votes:
> 1 - move to 16.3.2
> 1 - move to 3.4
> 2 - do not move
>
> If there are no other strong opinions, I'll leave it as-is.
>
> Best,
> -marina
>
>
> Marina Vatkina wrote:
>
> 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
>
>
>
>
> --
> Antonio Goncalves
> Software architect and Java Champion
>
> Web site <http://www.antoniogoncalves.org> | Twitter
> <http://twitter.com/agoncal> | Blog
> <http://feeds.feedburner.com/AntonioGoncalves> | LinkedIn
> <http://www.linkedin.com/in/agoncal> | Paris JUG <http://www.parisjug.org>