We document the TaskResultListener property of a job. However, we also document JobListener which has a more complete, finer grained set of features, and whose jobReturned() notifications are called the same number of times as TaskResultListener.resultsReceived(), thus introducing an unneeded and potentially confusing duplication of the functionality.

Furthermore, a lot of the client code relies on the JPPFResultCollector implementation of TaskResultListener. For instance, the client-side job persistence is only performed in JPPFResultCollector.resultsReceived(). Also the JPPFExecutorService relies heavily on the subclass FutureResultCollector.

We propose to deprecate the usage of the TaskResultListener in the public exposed APIs (essentially the getter and setter in JPPFJob) and make TaskResultListener and its implementations internal APIs. This also implies deprecating the related documentation, and rewriting the code snippets and examples so they use a JobListener instead.