geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-956) Remove "global JNDI space"
Date Thu, 15 Sep 2005 04:19:59 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-956?page=comments#action_12329386 ] 

David Jencks commented on GERONIMO-956:
---------------------------------------

Along with removing the global-jndi-name tag I'm cleaning up the schema by:

removing version="1.5" attribute
removing connection-manager-ref element (this might theoretically be useful but it should
use the gbean name component approach.  I don't think anyone is very likely to implement their
own connection manager.  If they do we'll put it back)
removing credential-interface element (not used)

I'm going to commit the removal, check the tck, and then add some code in a day or two to
strip the no-longer-valid elements out and warn the user.

> 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.0

>
> 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


Mime
View raw message