Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2600

Exception handling - Fix the exception handling in Seam

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Exception Handling
    • Labels:
      None

      Description

      Currently we have at least one serious race condition in our pages.xml
      exception handling, related to redirect/message passing. I can
      reproduce (JIRA case is open) lost messages on exception redirect.
      Also, clean up the #

      {exception} and #{handledException} stuff - which
      might fix the issue as a side effect. I want one exception instance I
      can access in EL, not two. I want to be able to call getRootCause() on
      it to unwrap the root exception. Of course the root cause is the one I
      specify in pages.xml as the one that is handled, but the #{exception}

      should always be the wrapper. In any case, a clear and reliable
      (working in all situations) strategy needs to apply here.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  christian.bauer Christian Bauer
                  Reporter:
                  shane.bryzak Shane Bryzak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: