[
http://jira.jboss.com/jira/browse/JBSEAM-1546?page=comments#action_12366654 ]
Chris Rudd commented on JBSEAM-1546:
------------------------------------
Yea, I see that now after working on JBSEAM-1277 and JBSEAM-1294. :(
Although before the filter handles the exception the existing Seam context is still valid.
So I guess in theory one could pull information about the request out of that. But it
probably falls under the realm of "potentially bad / unreliable" things to do )
Should there be an event "org.jboss.seam.exceptionRaied"
that fires immediatly prior to the handler being called?
-----------------------------------------------------------------------------------------------------------------
Key: JBSEAM-1546
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1546
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.3.0.ALPHA
Reporter: Chris Rudd
Priority: Minor
The new events raised by the Exceptions component are nice, but would it be beneficial to
raise and event before the handler is called so that one can interrogate the state of the
request before its modified by the handler. (see JBSEAM-1285 - I would like to get the
view that was being processed when the exeption occured.)
I propose adding the follwing lines to Exceptions.handle
Exceptions.java line 52:
public void handle(Exception e) throws Exception
{
if ( Contexts.isConversationContextActive() )
{
Contexts.getConversationContext().set("org.jboss.seam.exception", e);
}
+ Events.instance().raiseEvent("org.jboss.seam.exceptionRaised." +
cause.getClass().getName(), cause);
+ Events.instance().raiseEvent("org.jboss.seam.exceptionRaised", cause);
--
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