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

Exception in Seam Resource is Swallowed and Redirection to debug.seam Does not Work

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0.GA
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Linux, JBoss 5.1.0.GA

      Description

      When a Seam managed resource produces an exception the exception is swallowed, i.e. it is not logged. Furthermore, maybe this is also the source of the problem, the failed request is not redirected to the correct debug.seam URL.

      Steps to reproduce on JBoss 5.1.0.GA with Seam 2.2.0.GA:

      1. create a Seam resource that produces an exception (code attached)
      2. navigate to the Seam resource: /seam/resource/myresource

      Now instead of redirecting to /debug.seam?cid=<CID> the browser redirects to /seam/resource/debug.xhtml?cid=<CID> which of course does not exist, thus resulting in a 403 HTTP error.
      Furthermore the exception is not logged in the JBoss logs.
      When you manually navigate to /debug.seam?cid=<CID> the full exception trace is shown (serves also as a workaround).

      Example resource (requires existence of resource servlet in web.xml) is attached.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                elmarweber Elmar Weber
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: