]
Pete Muir updated JBSEAM-2600:
------------------------------
Fix Version/s: 2.1.0.BETA1
(was: 2.1.0.GA)
Exception handling - Fix the exception handling in Seam
-------------------------------------------------------
Key: JBSEAM-2600
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2600
Project: Seam
Issue Type: Feature Request
Components: Exception Handling
Reporter: Shane Bryzak
Fix For: 2.1.0.BETA1
Currently we have at least one serious race condition in our pages.xml
exception handling, related to redirect/message passing. I can
reproduce (JIRA case is open) lost messages on exception redirect.
Also, clean up the #{exception} and #{handledException} stuff - which
might fix the issue as a side effect. I want one exception instance I
can access in EL, not two. I want to be able to call getRootCause() on
it to unwrap the root exception. Of course the root cause is the one I
specify in pages.xml as the one that is handled, but the #{exception}
should always be the wrapper. In any case, a clear and reliable
(working in all situations) strategy needs to apply here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: