Re: [Hibernate-devel] Hibernate + JNDI

[Jon L. <jon...@xe...>]

I think this make sense...  Doing it this way means you have everything
related with persistenace (Connections and the SessionFactory) all bound to
the same JNDI tree.

The only example I can think of where you would have a datasource registered
with a different JNDI provider is if you lookup a remote data source from an
external J2EE container, and I think that is not exactly an everyday
occurance.

----- Original Message -----
From: <Gavin_King/Cirrus%CI...@ci...>
To: <hib...@li...>
Sent: Wednesday, June 05, 2002 2:07 PM
Subject: [Hibernate-devel] Hibernate + JNDI


> The code I just committed to CVS makes the SessionFactory bind itself to
> JNDI when the user specifies the property hibernate.session_factory_name.
> This allows BMP EJBs, for example, to obtain their SessionFactory with a
> JNDI lookup. I have a question about this: the way I've done it, we use
the
> same properties hibernate.jndi.url + hibernate.jndi.class for
> DatasourceCOnnectionProvider (which looks up a Datasource in JNDI) as for
> SessionFactory. Is there a strong reason to decouple these? ie. would it
be
> normal to have the Datasource registered with a different JNDI provider
> from the SessionFactory?
>
> I want to make this reasonably flexible without having an explosion of
> these hibernate.xxxx properties.....
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Hibernate-devel mailing list
> Hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>