You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/10/28 09:17:04 UTC

[jira] Updated: (GERONIMO-956) Remove "global JNDI space"

     [ http://issues.apache.org/jira/browse/GERONIMO-956?page=all ]

David Jencks updated GERONIMO-956:
----------------------------------

    Fix Version: 1.x
                     (was: 1.0)

> Remove "global JNDI space"
> --------------------------
>
>          Key: GERONIMO-956
>          URL: http://issues.apache.org/jira/browse/GERONIMO-956
>      Project: Geronimo
>         Type: Improvement
>   Components: connector, naming
>     Versions: 1.0-M4
>     Reporter: Aaron Mulder
>     Assignee: David Jencks
>      Fix For: 1.x

>
> Geronimo has a "global" JNDI space under "geronimo:".  However:
>  - it's only used by connectors, not EJBs
>  - it's not visible outside the current VM
> It doesn't seem like this is really benefitting anyone.  The effort necessary to make it behave like JNDI behaves in other popular app servers seems to be significant.  After talking on IRC, David J and I are soliciting feedback on removing this feature entirely for now.
> Note: this is different than the JNDI space that OpenEJB uses to expose EJBs to remote clients, which takes EJBs only and is obviously accessible to remote clients.  We are not proposing to change that at this time.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira