]
Brian Leathem updated RF-11128:
-------------------------------
Fix Version/s: 4.Future
Publish JSF 2.0 ExceptionQueuedEvent (instead of log.error)
-----------------------------------------------------------
Key: RF-11128
URL:
https://issues.jboss.org/browse/RF-11128
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: core
Environment: RF 4.1 develop
Reporter: Martin Kočí
Fix For: 4.Future
use JSF 2.0 ExceptionQueuedEvent
try {
//
} catch (Exception e) {
ExceptionQueuedEventContext exceptionQueuedEventContext = new
ExceptionQueuedEventContext(context, e, this, PhaseId.XYZ);
context.getApplication().publishEvent(context, ExceptionQueuedEvent.class,
exceptionQueuedEventContext);
}
instead of logging. Example: ExtendedPartialViewContextImpl logs exception as severe and
that prevents (custom) exception handler to handle that error.
Related issues from MyFaces:
#
https://issues.apache.org/jira/browse/MYFACES-3053
#
https://issues.apache.org/jira/browse/MYFACES-3198
#
https://issues.apache.org/jira/browse/MYFACES-3201
--
This message is automatically generated by JIRA.
For more information on JIRA, see: