[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1279) use ExceptionFilter in Remoting
by Keith Naas (JIRA)
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
12 years, 8 months
[JBoss JIRA] Created: (JBSEAM-4778) Valid URLs are ignored on Excel Stylesheet ULink components (CSSParser.java)
by Juan Francisco Ara Monzon (JIRA)
Valid URLs are ignored on Excel Stylesheet ULink components (CSSParser.java)
----------------------------------------------------------------------------
Key: JBSEAM-4778
URL: https://issues.jboss.org/browse/JBSEAM-4778
Project: Seam
Issue Type: Bug
Components: Excel
Affects Versions: 2.2.1.Final
Environment: Standard
Reporter: Juan Francisco Ara Monzon
Priority: Trivial
Fix For: 2.3.0.ALPHA
Valid URLs are not being processed correctly by CSSParser
If you load a URL with ftp/http format (http://) works perfectly, but if you reference a resource inside the application (i.e. classLoader.getResource("whatever").toString()) the parser doesn't recognices it as a valid URL
CSSParser discriminates between resources or urls by "://" but should be doing by ":/" (as in jar:/.... or vfszip:// returned from WEB-INF/classes/ files.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months