[
https://issues.apache.org/jira/browse/DROIDS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998034#comment-12998034
]
Bertil Chapuis commented on DROIDS-120:
---------------------------------------
Ok for me. Since the SimpleTaskQueue will probably be replaced by
java.util.Queue working on a finer ExceptionHandler is not the first priority.
I applied the patch and rescheduled the ticket for 0.0.2.
> Better exception handling in SimpleTaskQueue - merge
> ----------------------------------------------------
>
> Key: DROIDS-120
> URL: https://issues.apache.org/jira/browse/DROIDS-120
> Project: Droids
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.0.1
> Reporter: Eugen Paraschiv
> Fix For: 0.0.1
>
> Attachments: DROIDS-120_v2.patch
>
>
> In SimpleTaskQueue - merge, any exception in any of the individual tasks
> would end up in closing down the entire process and loosing all the results
> in that particular collection.
> This should not be the case - when iterating over a (possibly large)
> collection, where each result is relevant, an exception should be logged and
> the iteration should continue on to the next element.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
