[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3364) stacktrace _very_ confusing

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-3364.
-----------------------------

    Resolution: Won't Fix
      Assignee: Pete Muir


This will be reviewed when we upgrade to JSF2

> stacktrace _very_ confusing
> ---------------------------
>
>                 Key: JBSEAM-3364
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3364
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.2.SP1
>         Environment: jboss server 4.2.2.GA, eclipse 3.4 linux 32bit
>            Reporter: arne anka
>            Assignee: Pete Muir
>
> the stacktraces are 
> a) too long
> b) redundant
> c) sometimes totally useless
> b) the same information is shown again and again and again. but the really useful part (where it happens in _my_ code) is far far down and often rather hard to find. i think it would be sensible to re-organize the chain of exception throwing so that the exception from the project is on top and that not every level prints the same stacktrace over again.
> c) the other day i had a stacktrace that contained no information whatsoever (only the name of my xhtml), no linenumber, nothing.
> since i knew that it only could be caused by an empty id attribute (id="") i was able to fix that -- but that's pure coincidence. if seam knows what's wrong (and it has to, else no exception would have been thrown), it should under all circumstaces put out that information instead of a windows like "an error occured"
> see JBIDE-2631 for two stacktraces illustrating the issue.

-- 
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