Wojciech,
I am debugging a problem in one of our apps that I think may be caused by
this same issue. It looks like it is recreating the Configuration on every
request.. egads! I hestiate to add Poolable to HibernateServiceImpl
because that means that the container is now responsible for maintaining the
pool, and often it doesn't know when to add or release them.
You're right, if you declare it Poolable, users will have to explicitly call release() on it or nothing will get returned to the pool.
However, to be honest, I am a bit of a babe in the woods here.. I don't
really understand the poolable interface. I am using the code with the ECM
container, and I was always under the impression that it produced a
singleton versus a new one each time?
By default a new one is created at every request. A singleton is only created if you declare it ThreadSafe.
I don't use the HibernateService, so I'm afraid I can be of much more help than that.
-Mark
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
