Putting the SessionFactory in my application: good idea?

njvack · **Joined:** Mon Feb 16, 2004 3:56 pm **Posts:** 2

When setting up my first test Hibernate/Tomcat application, I've noticed that the servlet takes a measurable amount of time (1.5 sec) to read my mapping files and configure itself.

I'm thinking I'll put my SessionFactory in the application scope and handle its initalization in my servlet's init() method; is this a good idea or is it a trap?

Thanks in advance... I'm thrilled at the amount of work Hibernate will be able to save me here.

michael · **Posted:** Mon Feb 16, 2004 4:09 pm

Putting the SessionFactory in the application scope is perfectly fine. :)

emmanuel · **Posted:** Mon Feb 16, 2004 4:10 pm

njvack wrote:

I'm thinking I'll put my SessionFactory in the application scope and handle its initalization in my servlet's init() method; is this a good idea or is it a trap?

It's OK, people put it either in singleton, JNDI, etc... It's done for that.

njvack · **Joined:** Mon Feb 16, 2004 3:56 pm **Posts:** 2

Excellent... I've tried it and now my skeletal little app is really fast :)

Thanks a million!