[
https://issues.apache.org/jira/browse/PIVOT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553173#comment-14553173
]
Roger Whitcomb commented on PIVOT-969:
--------------------------------------
I want to run some tests to see if this patch actually has any effect. It
occurred to me that where we really need the uncaught handler is way outside
this realm (i.e., before the ExecuteCallback is even created, perhaps). So,
I'm not sure this change will even have any effect. But I do have a fail case
in our application that I can test with.
> Better handle uncaught exceptions in background threads in Pivot
> ----------------------------------------------------------------
>
> Key: PIVOT-969
> URL: https://issues.apache.org/jira/browse/PIVOT-969
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Affects Versions: 2.0.4, 2.1
> Environment: All
> Reporter: Roger Whitcomb
> Assignee: Roger Whitcomb
> Priority: Minor
> Labels: exception-reporting, uncaught-exceptions
> Fix For: 2.1
>
> Attachments: task.patch
>
>
> PIVOT-916 regularized the handling of uncaught exceptions in most places in
> the GUI thread and during startup. But background threads can still
> basically ignore uncaught exceptions. But using the
> Thread.setDefaultUncaughtExceptionHandler and changing some of our interfaces
> (namely Application.UncaughtExceptionHandler) we could use the
> ApplicationContext.handleUncaughtException as the default exception handler
> (which delegates to an application's override method).
> This would involve changing the signature (or adding an override method) that
> accepts (Thread, Throwable) in both ApplicationContext and
> Application.UncaughtExceptionHandler interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
