JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
task_small.png
CLOSED  Task JPPF-296  -  Rename SubmissionStatusXXX classes into JobStatusXXX
Posted Jul 26, 2014 - updated Oct 22, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Task
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
For consistency of the APIs, we rpopose to rename the following client classes:
  1. org.jppf.client.submission.SubmissionStatus
  2. org.jppf.client.submission.SubmissionStatusHandler
  3. org.jppf.client.submission.SubmissionManager
  4. org.jppf.client.event.SubmissionStatusEvent
  5. org.jppf.client.event.SubmissionStatusListener
  6. org.jppf.client.balancer.SubmissionManagerClient
into:
  1. org.jppf.client.JobStatus
  2. org.jppf.client.JobStatusHandler
  3. org.jppf.client.JobManager
  4. org.jppf.client.event.JobStatusEvent
  5. org.jppf.client.event.JobStatusListener
  6. org.jppf.client.balancer.JobManagerClient
The methods that use these classes explicitely should be renamed accordingly with consistency in mind (e.g. getSubmissionSatus() --> getJobStatus()).

These changes will require doc changes, especially for the J2EE connector. They will also need to be added tot he API changes document.


#3
Comment posted by
lolo4j
Oct 22, 18:21
implemented in trunk revision 3441