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

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on JBAS-9224:
--------------------------------------

For Hibernate, as a "pesky legacy subsystems" that uses a standard Java-defined API {{Context#bind}} to attempt to make users lives easier, what do you suggest we do?



> 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