[jboss-jira] [JBoss JIRA] Commented: (JBAS-9224) Automatic JNDI implementation

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594028#comment-12594028 ] 

David Lloyd commented on JBAS-9224:
-----------------------------------

Nice, Steve. :)

To bind things into JNDI your corresponding subsystem must go through the service layer.  Otherwise, if things express an injection dependency on a JNDI binding it will not start in the right order and the whole thing falls apart.  Note that there's nothing in the EE spec that says that the "java:" JNDI context should be writable by the user.

The mechanism specified in the description allows things which inflexibly require JNDI binding to be effectively faked out so that it can still work, at the cost of some perf.

> Automatic JNDI implementation
> -----------------------------
>
>                 Key: JBAS-9224
>                 URL: https://issues.jboss.org/browse/JBAS-9224
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: EE, Naming
>            Reporter: David Lloyd
>            Assignee: John Bailey
>            Priority: Critical
>             Fix For: 7.0.0.Beta3
>
>
> The JNDI subsystem should become fully service-oriented, meaning:
> 1) Contexts are always read-only
> 2) The NamingStore is populated solely by services
> 3) When the last binding in a context is removed, the context is automatically removed
> For pesky legacy subsystems which still expect to be able to bind into Context, we could possibly make up a "fake" Context from which the bound ObjectFactory (or whatever) is extracted to create the "real" service.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira