JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
task_small.png
CLOSED  Task JPPF-152  -  Refactor the client API to provide access to connections organized into pools
Posted Jun 02, 2013 - updated Mar 08, 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
     lolo4j
  • Estimated time
    Not estimated
  • Time spent
    No time spent
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1
Issue description
Currently, the APIs to introspect the existing connections do not make much sense. In particular, they do no reflect the organization into connection pools, as allowed in the configuration. They also do not make it easy to know which connection is connected to which driver, nor to which pool it belongs.

We need to refactor the client APIs to make the navigation of the set of connections both logical and meaningful.

#5
Comment posted by
 lolo4j
Mar 06, 07:43
implemented in trunk revision 3065