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

Exception handling - Never try to do anything after an exception but exception handling

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: None
    • Fix Version/s: 2.1.0.BETA1
    • Component/s: Core
    • Labels:
      None

      Description

      This is related to JBSEAM-2595

      Currently, if no exception handler is defined
      for an exception, Seam will (after logging and swallowing in
      SeamPhaseListener) happily continue with the next phase. It WILL fall
      over and blow up with another exception in almost all cases,
      especially if the rendering triggers any database access. These are
      the famous "Transaction is not active" exceptions that THEN will
      appear on the page. There is no hint of the real cause, the swallowed
      exception. Not even a "check in the log, idiot" message. We need to
      figure out if the default exception handler (without pages.xml) as
      proposed in 1. is sufficient to solve this issue. I'm not sure about
      RENDER RESPONSE exceptions.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  shane.bryzak Shane Bryzak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: