[
https://issues.apache.org/jira/browse/PIVOT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Whitcomb updated PIVOT-969:
---------------------------------
Attachment: task.patch
The file "task.patch" has what I consider a good first step for this, that
doesn't break backward compatibility, and yet addresses this issue for all the
standard background "Task" operations (and subclasses).
Comments? Suggestions?
> 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)
