By the time it executes, it is too late to render a response with the exception. There's nothing that can catch the exception ... the only thing "above" ThreadCleanupHubImpl is the servlet and then the servlet container. Further, it is very important that every cleanup listener be invoked, or you could experience some memory leaks in the application, as threads hold onto objects inside ThreadLocals.
On Jan 11, 2008 2:33 PM, Franz Amador <[EMAIL PROTECTED]> wrote: > ThreadCleanupHubImpl.cleanup (line 53) catches exceptions thrown by service > initialization cleanup. It logs them, which is good, but it doesn't pass > them up, which is causing me problems. I want to know if Hibernate > initialized successfully, but this prevents me from seeing exceptions thrown > during the transaction commit in > HibernateSessionManagerImpl.threadDidCleanup. Is this an oversight or is > there a design goal of having the Registry come up no matter what? > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
