[seam-issues] [JBoss JIRA] Issue Comment Edited: (SEAMREMOTING-14) use ExceptionFilter in Remoting

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Sun Jan 30 06:29:50 EST 2011


    [ https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578911#comment-12578911 ] 

Jozef Hartinger edited comment on SEAMREMOTING-14 at 1/30/11 6:27 AM:
----------------------------------------------------------------------

IMHO, the best way to do this with Seam 3 is to route the request through Seam Catch by firing Event<ExceptionToCatch> if an exception occurs.

This should be optional based on whether Seam Catch is on classpath, so perhaps adding a @Specialized ExecutionHandler that implements the catch integration and is activated if Catch is on classpath is the way to go. 

Plus a qualifier like @RemotingRequests so that the exceptions can be filtered.

      was (Author: jharting):
    IMHO, the best way to do this with Seam 3 is to route the request through Seam Catch by firing Event<ExceptionToCatch> if an exception occurs.

This should be optional based on whether Seam Catch is on classpath, so perhaps adding a @Specialized ExecutionHandler that implements the catch integration and is activated if Catch is on classpath is the way to go.
  
> use ExceptionFilter in Remoting
> -------------------------------
>
>                 Key: SEAMREMOTING-14
>                 URL: https://issues.jboss.org/browse/SEAMREMOTING-14
>             Project: Seam Remoting
>          Issue Type: Feature Request
>            Reporter: Keith Naas
>            Assignee: Shane Bryzak
>
> 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:
> # 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.
> # 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.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list