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)" <ji...@apache.org> on 2010/06/02 09:39:38 UTC
[jira] Commented: (GERONIMO-5025) New module/app/global jndi
contexts in javaee 6 spec
[ https://issues.apache.org/jira/browse/GERONIMO-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874475#action_12874475 ]
David Jencks commented on GERONIMO-5025:
----------------------------------------
rev 950397 (see also GERONIMO-5117) moves jndi support directly into Modules and straightens out when contexts are shared between submodules and ears and modules.
> New module/app/global jndi contexts in javaee 6 spec
> ----------------------------------------------------
>
> Key: GERONIMO-5025
> URL: https://issues.apache.org/jira/browse/GERONIMO-5025
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: deployment, naming
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> Javaee platform spec describes some new jndi java: contexts that are more shared between components.
> java:comp (existing)
> java:module
> java:app
> java:global
> My first idea for implementing this:
> 1. in RootContext, have the thread local represent java: rather than java:comp. So all the namespaces will be in the Context object.
> 2. Construct this Context by federating objects for each scope. We'll have to maintain a global context somewhere. The others can presumably be constructed during deployment and set up in the existing gbeans for the app components.
> 3. Modify the naming builders to put stuff into the right namespace.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.