I have a route("parent route") with a global onException() method that contains
an Error Processor(). I can see that this is hit when an error is generated
from within this route.
I have a route("child route") that has no onException(). It is called by the
parent route. It throws an exception (eg. ExecException from exec endpoint). I
would expect the exception to bubble up and be caught by the parent route. This
does not happen.
If I add a LoggingErrorHandler() to the parent route, I can see the error
logged.
If I add the same onException() to the child route as is on the parent, I can
see the exception being caught.
Once the child route throws the exception is it no longer an exception but an
error? Can the parent route's global onException() be used in the manner that I
am attempting?
Thanks,
Damian.
________________________________
This communication (and any attachments) is directed in confidence to the
addressee(s) listed above, and may not otherwise be distributed, copied or
used. The contents of this communication may also be subject to privilege, and
all rights to that privilege are expressly claimed and not waived. If you have
received this communication in error, please notify us by reply e-mail or by
telephone and delete this communication (and any attachments) without making a
copy.
Before opening or using attachments, you should check them for viruses and
defects. We do not accept liability in connection with computer virus, data
corruption, delay, interruption, unauthorised access or unauthorised amendment.
