JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-262  -  Integrate the functionality of JPPFResultCollector into JPPFJob
Posted May 11, 2014 - updated Aug 31, 2014
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
This relates to Feature request JPPF-260 - Deprecate usage of TaskResultListener in exposed APIs. Since JPPFResultCollector will become an internal-only API, this should allow us to resolve an inconstency in the client APIs, namely that to get the results of a non-blocking job execution we need to use a separate class JPPFResultCollector and call its awaitResults() method. The awaitResults() method, along with getAllResults(), should be part of the JPPFJob API.