JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-444  -  Fluent interfaces
Posted Mar 29, 2016 - updated Feb 25, 2017
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
    Enhancement
  • 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
    Core
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
This is about making the JPPF APIs fluent wherever applicable, as we have already done for the configuration API.

Basically, we want to refactor the modifiers in these public APIs such that they return an instance of the object they modify without type casting. This allows method calls chaining and makes the code both more readable and more compact. When the modifiers belong to multiple classes in the same class or interface hierarchy, we might need to genericize them to use the compiler's inherent type inference capabilities.

Some candidate APIs:
  • job SLA
  • JPPFJob / AbstractJPPFJob
  • Metadata / Metadata
  • Task / AbstractTask hierarchy
  • ... ?



#4
Comment posted by
 lolo4j
Feb 25, 09:49
Implemented in trunk revision 4421