[
https://issues.apache.org/jira/browse/PIVOT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582336#comment-14582336
]
Roger Whitcomb commented on PIVOT-969:
--------------------------------------
Ooops! Build was broken.
Fix that and do some more rearranging:
Sending wtk\src\org\apache\pivot\wtk\ApplicationContext.java
Sending wtk\src\org\apache\pivot\wtk\BrowserApplicationContext.java
Sending wtk\src\org\apache\pivot\wtk\DesktopApplicationContext.java
Transmitting file data ...
Committed revision 1684960.
> 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: handler.diffs, 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)
