From: Gavin_King/Cirrus%<CI...@ci...> - 2002-06-05 12:22:19
|
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..... |