Helloo,

Id like to get your opinion for the best way to use hibernate spring and JSf web app,
I have 2 separate project, the first one, use hibernate and spring to manage DAO objects; the second is the JSF web app,
the application context file is stored on the hibernate project, so on the web app I just do like that:



hollowing out, the hibernate session is not saved between 2 calls, It would be a bite slowly..
what's the best ay to share hibernate session and let the projects independents.?

no idea..???

never keep database (or any other restricted) resources open in between http requests.
It's a recipe for disaster.

so , open/close hibernate session for each data babse call does not reduce performance??

if you use connection pooling it should be minimal.
And you're saving yourself a lot of headaches with connection starvation if your load goes up or clients don't close their sessions properly (most users tend to just close their browser window rather than use your "logout" button to tell the server they're done).

Im using spring with hibernate.
I talk about hibernate session..I dont manage connection pooling..
on the web app i cannot even use the dynamic feetching..so, I dont take advantage of persistence..

Either Spring or Hibernate can provide your connection pool.
A Hibernate session is linked to a database connection, you don't want to hold onto that connection any longer than absolutely necessary.

If you configure a connection pool the performance penalty for closing the connection in between http requests should be minimal.

I've seen the results of applications holding on to connections too long. Connection starvation causes database servers to hang or crash, sometimes with disastrous results (loss of data integrity, but far more frequently "just" lost productivity and frustrated DBAs and system administrators).

Just take a look at the open session in view pattern:

http://www.hibernate.org/43.html

Basically, in a web app what you want is to create one session factory and then open and close sessions on each request. Connection pooling takes care of leaving enough connections to your database so that performance is good.