Hi All, I've been using the tapestry-hibernate module without a problem until i faced the following scenario
I have a entity called profile with a many to one association with the entity user. suppose that i have the profile P associated with some user U in the database so if try to delete P a foreign key constraint will complaint and an hibernateException will be throw. The first time that i execute this operation i have no problems but the second time the web server is not responding, and i have to kill the process. I think the connexion pool is locking to himself, but the problem seems that when i detect the hibernateException and then with the HibernateSessionManager call the abort() method, the session is not discarted and when the ThreadHubCleanup call the commit, it tries to execute the delete again. by the way i am using SQL Server. and T 5.0.6 do you thing this is a bug or i am missing something? Thanks in advance Cesar. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
