[hibernate-issues] [Hibernate-JIRA] Commented: (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:comment-tabpanel&focusedCommentId=44766#comment-44766 ] 

Steve Ebersole commented on HHH-6822:
-------------------------------------

Added {{hibernate.session_factory_name_is_jndi}} which is a boolean indicating whether {{hibernate.session_factory_name}} is a JNDI name (as opposed to a simple name intended only for cross-VM serialization).  The value defaults to {{true}} in order to maintain backwards compatibility.

In order to provide across VM serialization all you have to do is to name the {{SessionFactory}}.  In fact that was always the case.  What has changed is that in the past, doing so required that JNDI be available and writeable; the {{SessionFactory}} was written into that JNDI namespace.  This new setting simply lets this naming be used without JNDI.

> 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
>
>          Time Spent: 1h 55m
>
> 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