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

Julien Kronegg (JIRA) jira-events at lists.jboss.org
Tue Aug 5 17:58:56 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBSEAM-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12423744#action_12423744 ] 

Julien Kronegg commented on JBSEAM-3052:
----------------------------------------

The scenario was the following: a Seam xhtml page was getting a value from a bean which first get a database list X (read only, no write), then build the value to return based on the list X. Because the value to return was built based on X.get(0), an IndexOutOfBoundException is raised when X.size()==0.

It is important to note that the "isRollbackRequired(e)" is false (hence no rollback). So the stacktrace is displayed on the System.err just before the "throw e;".
The IndexOutOfBoundsException is consequently thrown but is swallowed in the RollbackInterceptor.aroundInvoke caller.
The next step(s): find where...


> Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle
> -------------------------------------------------------------------------
>
>                 Key: JBSEAM-3052
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3052
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Exception Handling
>    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/TransactionIsNotActiveWithCreateAnnotation
> 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!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list