I am looking through the code and trying to figure this out --
With the default behavior of Hibernate which is used --
EntityPersister creates a cache of java.sql.PreparedStatements for each object --
Is this default behavior ?
And Is it used in all cases...

Huh?

EntityPersister does no such thing....

I told you two times how PreparedStatement caching with Hibernate works. Don't you believe me?

Not saying I don't -- I am haveing to prove it to others -- with in a container JBoss--
Yet with limited Docs it is hard to understand how it is done --
The person I am trying to prove this out too wants to write a secondary connection pool --and has that PS for each object and associate them with each connection....

Now there must be an easier way...
and that is what I am looking for-- I do not want to re-create the breadbox and I do not want to try to solve a problem that does not exist..
I am trying to understand how using C3P0 with-in a container will help...
Not to mention -- Limited Docs on C3PO as well...

You can easily activate PreparedStatement caching for JBoss by setting <prepared-statement-cache-size >100 </prepared-statement-cache-size > in your datasource. There is no problem, and certainly nothing to dig out in the Hibernate source, because as I said hibernate does NOT do PreparedStatement caching but leaves that to the DB pool.

PS: JBoss >= 3.2.2 only

We are using JBoss 3.2.3 ---

Well so it should work for you.

Many Thanks -- and I apologize if I seemed to be a pessimist

You are welcome - no need to apologize for anything as long as you can withstand an occasional grumpy comment ;) Have fun with Hibernate.