8:32 a.m.
use ExceptionFilter in Remoting
-------------------------------
Key: JBSEAM-1279
URL: http://jira.jboss.com/jira/browse/JBSEAM-1279
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Affects Versions: 1.2.1.GA
Reporter: Keith Naas
Assigned To: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1279) use ExceptionFilter in Remoting
[ http://jira.jboss.com/jira/browse/JBSEAM-1279?page=comments#action_12401926 ]
Pete Muir commented on JBSEAM-1279:
-----------------------------------
I'm not sure this makes sense as the ExceptionFilter is for JSF requests and not
relevant for other clients like remoting.
use ExceptionFilter in Remoting
-------------------------------
Key: JBSEAM-1279
URL: http://jira.jboss.com/jira/browse/JBSEAM-1279
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Affects Versions: 1.2.1.GA
Reporter: Keith Naas
Assigned To: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1279) use ExceptionFilter in Remoting
[ http://jira.jboss.com/jira/browse/JBSEAM-1279?page=comments#action_12401984 ]
Keith Naas commented on JBSEAM-1279:
------------------------------------
The ExceptionFilter doesn't have to only be for JSF requests :)
Even if the ExceptionFilter is not used, something could be changed so that the right Http
Status Codes are returned to the browser. For instance, instead of receiving no content
with an Http 200 response, one would get 403 for NotAuthorized and 401 for NotLoggedIn?
use ExceptionFilter in Remoting
-------------------------------
Key: JBSEAM-1279
URL: http://jira.jboss.com/jira/browse/JBSEAM-1279
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Affects Versions: 1.2.1.GA
Reporter: Keith Naas
Assigned To: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1279) use ExceptionFilter in Remoting
[ http://jira.jboss.com/jira/browse/JBSEAM-1279?page=comments#action_12402016 ]
Pete Muir commented on JBSEAM-1279:
-----------------------------------
The current implementation does.
use ExceptionFilter in Remoting
-------------------------------
Key: JBSEAM-1279
URL: http://jira.jboss.com/jira/browse/JBSEAM-1279
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Affects Versions: 1.2.1.GA
Reporter: Keith Naas
Assigned To: 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:06 p.m.
New subject: [JBoss JIRA] Commented: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://jira.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.plu...
]
Shane Bryzak commented on SEAMREMOTING-14:
------------------------------------------
Still need to look at exception handling in Seam 3
use ExceptionFilter in Remoting
-------------------------------
Key: SEAMREMOTING-14
URL: https://jira.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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:06 p.m.
New subject: [JBoss JIRA] Moved: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://jira.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.plu...
]
Shane Bryzak moved JBSEAM-1279 to SEAMREMOTING-14:
--------------------------------------------------
Project: Seam Remoting (was: Seam)
Key: SEAMREMOTING-14 (was: JBSEAM-1279)
Affects Version/s: (was: 1.2.1.GA)
Component/s: (was: Remoting)
use ExceptionFilter in Remoting
-------------------------------
Key: SEAMREMOTING-14
URL: https://jira.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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 a.m.
New subject: [JBoss JIRA] Commented: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
Jozef Hartinger commented on SEAMREMOTING-14:
---------------------------------------------
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
5:29 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
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
5:29 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
Jozef Hartinger edited comment on SEAMREMOTING-14 at 1/30/11 6:28 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 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.
Plus a qualifier like @RemotingRequests so that the exceptions can be filtered.
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
6:19 a.m.
New subject: [JBoss JIRA] Updated: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
Shane Bryzak updated SEAMREMOTING-14:
-------------------------------------
Fix Version/s: 3.0.0.CR1
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: 3.0.0.CR1
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
11:56 p.m.
New subject: [JBoss JIRA] Updated: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
Shane Bryzak updated SEAMREMOTING-14:
-------------------------------------
Fix Version/s: 3.0.0.Final
(was: 3.0.0.CR1)
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: 3.0.0.Final
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
7:06 p.m.
New subject: [JBoss JIRA] Updated: (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
Shane Bryzak updated SEAMREMOTING-14:
-------------------------------------
Fix Version/s: 3.1.0.Final
(was: 3.0.0.Final)
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: 3.1.0.Final
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
7:24 p.m.
New subject: [JBoss JIRA] (SEAMREMOTING-14) use ExceptionFilter in Remoting
[
https://issues.jboss.org/browse/SEAMREMOTING-14?page=com.atlassian.jira.p...
]
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
4717
days inactive
6339
days old
12 comments
5 participants
participants (5)
-
Jozef Hartinger (JIRA) -
Keith Naas (JIRA)
-
Pete Muir (JIRA)
-
Shane Bryzak (JIRA)
-
Shane Bryzak (Updated) (JIRA)