static vs. JNDI

aharvey · **Joined:** Tue Nov 11, 2003 6:24 pm **Posts:** 17

Could someone explain the pros and cons of placing a Hibernate SessionFactory into a static variable in the VM vs. inside JNDI for a web application?

Our application places SessionFactory into JNDI and we've found this to be problematic for testing our business logic with JUnit. We're consider just storing SessionFactory as a static in a singleton helper class. Is there a downside to this that I am unaware of?

l.masini · **Posted:** Fri Feb 06, 2004 10:18 am

Why not simply a singleton that can use JNDI in a web-app and a static variable in a JUnit test ?
Ciao.

christian · **Posted:** Fri Feb 06, 2004 10:25 am

There is no difference, both implement the Registry pattern. Depends on what your other frameworks or your application uses.

christian · **Posted:** Fri Feb 06, 2004 10:25 am

Oh, and JNDI is a standardized Registry API :)

ko5tik · **Posted:** Fri Feb 06, 2004 12:18 pm

aharvey wrote:

Our application places SessionFactory into JNDI and we've found this to be problematic for testing our business logic with JUnit. We're consider just storing SessionFactory as a static in a singleton helper class. Is there a downside to this that I am unaware of?

It's still possible to use in unit tests. Just populate context yourself.

Placing session factory in JNDI gives you advantages if you like to
be able to exchange / reconfigure session factory without restarting
web app, or share it between 2 webapps / ejb tiers / whatever

karaznie · **Joined:** Tue Jan 27, 2004 3:26 pm **Posts:** 18

aharvey wrote:

Our application places SessionFactory into JNDI and we've found this to be problematic for testing our business logic with JUnit.

Try 'JUnit JNDI DataSource helper package' (http://www.javaranch.com/codebarn.jsp).

regards,
Artur