[
https://issues.apache.org/jira/browse/GERONIMO-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803554#action_12803554
]
David Jencks commented on GERONIMO-5025:
----------------------------------------
rev 901935 basically does the work described above. There aren't really any
tests yet.
More stuff to do:
1. detect if an entry is specified twice and object if it is specified
differently.
2. find out what is meant for web apps about java:comp and java:module being
"the same"
3. figure out if/how to get the global context available to app clients.
Also we could probably have a urlHandler for jca: and ger: contexts. What we
used to do was bogus, treating the "scheme" part as a name component.
> 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: New Feature
> 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.
