Implements a default error handling class for the ADF framework. This handler caches the exception in the bindingContainer and then if 'Throw' flag is set, throws exceptions it receives as JboExceptions (by creating a JboException if required).As far as I understand this the handler re throws the exception is you pass true to the base constructor, otherwise it only processes the exception.
... As far as I understand this the handler re throws the exception is you pass true to the base constructor, otherwise it only processes the exception.Do you know of a scenario where this will make a difference, and how or where this difference can be seen?
I think that using "false" is the correct implementation to use. ...So, would you consider "Example 28-26 Custom Error Handler" and "Example 28-27 Default Constructor", both suggesting to pass true, to be a documentation bug?
... I don't have a use case for this, but in effect what happens is that you would change the behavior from reporting errors to the user to an exception handled by the developer (e.g. forcing a redirect)Because I don't see any difference in behaviour, I still don't understand the difference. Maybe you can post a scenario or some code (not necessarily a "use-case") that can illustrate the difference in behaviour?
The flag simply affects how this error handler will honour the exception. Ifthe throw flag is on, reportException will 'additionally' throw the exceptionat the end of the method while if false, then reportException simply cachesthe exception in the bindingContainer and returns letting the frameworkcodepath to complete it's lifecycle and potentially perform all the updatesor steps in the page lifecycle.Somehow this is still not very clear to me, hence the following questions:
In web scenario, throw=false prevents the pageLifecycle from aborting at thefirst exception.