[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Bryzak updated SEAMREMOTING-14:
-------------------------------------
Fix Version/s: Future
(was: 3.1.0.Final)
Forum Reference: http://community.jboss.org/thread/135773?tstart=0 (was:
http://community.jboss.org/thread/135773?tstart=0)
Bumping this for now - we've done some work on exception handling in the client
but integration with Catch might still be worthwhile.
> 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
> Fix For: Future
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
