Hi !

I am implementing a set of web services. Each of them using Hibernate when accessing the database.

The problem is a follows: Everytime a webservice is invoked, Hibernate starts it's initialization of the SessionFactory, reading all the mapping-files etc... Very time consuming.

Is there an easy way to avoid all this startup. That is: Do it once and keep the SessionFactory somewhere until the next time it is needed.

In the Hibernate-doc it says someting like:
"..A SessionFactory is usually only build once, e.g. at startup with a load-on-startup servlet. This also means you should not keep it in an instance variable in your servlets, but in some other location"

Sounds like a good thought, but I have not found any examples on how this is done.

Do anyone have any ideas on how to solve my problem??

Thanks!

Ted

Two options that I have used with different application are:
- a singleton instance of the session factory. (using a custom factory or delegating to an IOC container like Spring).
- JNDI - supported in by hibernate through configuration file.

What app server are you using?

Hi !
The app server is JBoss 4.0.2.

Thank you for you suggestions.
Do you also now if there are any examples available for the two approaches anywhere..?

Ted

Take a look at the following:

http://www.laliluna.de/first-hibernate- ... orial.html
http://hibernate.org/42.html

There are a lot of examples on the Hibernate and Spring sites.