[
https://issues.apache.org/jira/browse/PIVOT-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193853#comment-16193853
]
Roger Whitcomb commented on PIVOT-1009:
---------------------------------------
Add this feature, along with a new listener "WTKTaskListener" that implements
calling the ApplicationContext.uncaughtExceptionHandler for the task fault, and
including the background thread context the Task was run under.
Sending core\src\org\apache\pivot\util\concurrent\Task.java
Adding wtk\src\org\apache\pivot\wtk\WTKTaskListener.java
Transmitting file data ..done
Committing transaction...
Committed revision 1811271.
> Improve Task to be able to tell what the background Thread that was used to
> execute it
> --------------------------------------------------------------------------------------
>
> Key: PIVOT-1009
> URL: https://issues.apache.org/jira/browse/PIVOT-1009
> Project: Pivot
> Issue Type: Improvement
> Components: core-beans, wtk
> Environment: All
> Reporter: Roger Whitcomb
> Assignee: Roger Whitcomb
> Priority: Minor
> Fix For: 2.1
>
>
> The idea is that Tasks are generally run on a background thread, but we don't
> usually know what that thread was. There should be a field inside the Task
> class that keeps a weak reference to the thread ("weak" so it doesn't hold up
> garbage collection). That way any errors caught during the task execution
> can actually report the thread that was used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
