When an exception is throwed by a Listener that marks the Transaction as RollbackOnly we should have a default ExceptionHandler that displays a custom page that leverage the information contained in the Exception rather that displaying a generic error.
The first use case is for Quota management : when the listener break the transaction to enforce the Quota Management we should be able to display the user that the operation can not be done because of the Quota rules.
There are several steps :
- manage correctly the Exception bubbling
- Intercep the exception at a point we can actually do something
- manage the Seam state
|Allow correct Exception Bubbling from the Core to the UI Layer||Resolved|
|Add Seam level Exception Interceptor||Resolved|
|Better manage Dirty State in Navigation Context||Resolved|