Uploaded image for project: 'Seam Remoting'
  1. Seam Remoting
  2. SEAMREMOTING-14

use ExceptionFilter in Remoting

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Feature Request
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • Future
    • None

    Description

      Currently, the Remoting resource class swallows all exceptions. Because of this, it is not possible to gracefully handle security restrictions in WebRemote methods from the client.

      Two ideas:

      1. Simply bubble the Exception all the way up through the ResourceServlet. If the ResourceServlet throws the exception, the ExceptionFilter should pick up on it. The XHR would then receive the proper error code as defined in the pages.xml and could properly redirect the user to the correct login page.
      2. Have the ResourceServlet trap for NotLoggedInException's or NotAuthorizedException's and return the respective HTTP status code. The XHR would then receive the error code and be able to redirect the user to the correct login page.

      Attachments

        Issue Links

          Activity

            People

              sbryzak@redhat.com Shane Bryzak
              knaas_jira Keith Naas (Inactive)
              Archiver:
              samahaja@redhat.com Sagar Mahajan

              Dates

                Created:
                Updated:
                Archived: