[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3052) Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle

Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle ------------------------------------------------------------------------- Key: JBSEAM-3052 URL: http://jira.jboss.com/jira/browse/JBSEAM-3052 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.2.GA Environment: JBoss AS 4.2.2 Seam 2.0.2 Reporter: Peter Maedel Lots of people have been dealing with the issue of overwritten exceptions: http://www.seamframework.org/Community/ConnectionProblem http://www.seamframework.org/Community/TransactionIsNotActiveWithCreateAn... Although in some cases this behaviour is part of EJB specification (EJB Container overwriting Exception) I am unsure if there isnt a possibility within Seam to print exceptions when they occure rather than have them overwritten with useless junk (cannot open connection, transaction is abort_only) later on. If you want to reproduce try opening a page that references a bean with this @create method: @Create public void iCrash(){ new File("nonExistentDirectory").listFiles(); } Subsequent calls which involve Transactions (either in @create method or referenced beans) will result in the obscure "Transaction is abort_only" exception, leaving no trace which could lead to the actual cause of the failure. Honestly this behaviour has been a horrible waste of time so far!