JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Task JPPF-167  -  Refactor the client API so that standalone and JCA client use the same code
Posted Jul 13, 2013 - updated Jul 13, 2013
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 4.0
Issue description
The code in JPPFJcaClient, JPPFJcaClientConnection and JcaClassServerDelegate and the corresponding standalone client classes JPPFClient, JPPFClientConnectionImpl and ClassServerDelegateImpl, is so similar that I don't see the point of having different classes.

I propose to refactor the client code such that we only use one set of classes, no matter which kind of client we use.

Comment posted by
Jul 13, 12:40
Fixed. Changes committed to SVN trunk revision 2787.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.