JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-173  -  Ability to include external configuration in the JPPF configuration
Posted Jul 27, 2013 - updated Jul 30, 2013
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
  • Progress
       
  • 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 4.0
Issue description
This is about the ability to include external configuration files or configuration sources within the JPPF configuration initially specified for a client, server or node.

For instance we could have the following syntax: The last syntax refers to a class implementing JPPFConfiguration.ConfigurationSource

For convenience, we could also propose to have a configuration source which provides a Reader instead of an InputStream, such as:
public interface ConfigurationSourceReader {
  Reader getPropertyReader() throws IOException;
}

#4
Comment posted by
 lolo4j
Jul 30, 21:38
Implemented. Changes committed to SVN trunk revision 2835

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.