[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-6822) Split notions of (1) "naming" a SessionFactory and (2) specifying a JNDI name to which to bind it

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole updated HHH-6822:
--------------------------------

    Fix Version/s:     (was: 4.1.0)
                   4.0.1

> Split notions of (1) "naming" a SessionFactory and (2) specifying a JNDI name to which to bind it
> -------------------------------------------------------------------------------------------------
>
>                 Key: HHH-6822
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6822
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.0.1
>
>
> Currently naming a {{SessionFactory}} and specifying the JNDI namespace into which Hibernate should bind it after creation are one-in-the-same.  Ideally this should be split.  
> The concept of a named {{SessionFactory}} is useful in quite a few situations internally (the JNDI binding is more end user focused).  See {{org.hibernate.internal.SessionFactoryRegistry}}.

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