[
http://jira.jboss.com/jira/browse/JBSEAM-1016?page=all ]
Shane Bryzak closed JBSEAM-1016.
--------------------------------
Fix Version/s: 1.2.1.GA
Resolution: Done
Assignee: Shane Bryzak
I see no harm making these methods protected. Implemented in CVS. As to your other
requirement, exceptions are already stored in conversation scope when they occur - see
org.jboss.seam.core.Exceptions.
Change visibility of some methods in ExceptionFilter
----------------------------------------------------
Key: JBSEAM-1016
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1016
Project: JBoss Seam
Issue Type: Feature Request
Environment: Seam 1.2.0Patch1
Reporter: Leszek Kowalski
Assigned To: Shane Bryzak
Fix For: 1.2.1.GA
It would be really nice if visibility of methods endWebRequestAfterException and
rollbackTransactionIfNecessary could be changed from private to protected, so
ExceptionFilter could be subclassed easily (for example to add some custom code if an
exception occurs).
--
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