[ http://issues.apache.org/jira/browse/GERONIMO-956?page=comments#action_12320671 ]
Jeremy Boynes commented on GERONIMO-956: ---------------------------------------- There are quite a few applications out there that access the global JNDI directly to lookup resources. This is non-standard behaviour but for them we can either force them to change or provide a context they can use - this was meant to support them. This is probalby less essential now that we have a directory integrated, but on the other hand it probably is a lot lighter in weight. > 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 > 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
