Yes, as I've been using HibernateService with Fortress, I haven't had the need to implement the (deprecated) ThreadSafe interface (with fortress you declare the lifestyle with meta data). But as the code itself is threadsafe, adding ThreadSafe marker interface should fix the issue you are experiencing.
Rgds, Neeme
Wojciech Gdela wrote:
Mark Woon wrote:
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.
Yes, and I think that declaring HibernateServiceImpl as ThreadSafe is good solution to the problem.
------------------------------------------------------- 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
