JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-210  -  Add new execution policy executing an arbitrary script
Posted Dec 21, 2013 - updated Dec 24, 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
We propose to add a new type of execution policy, which executes an arbitrary script in an available dynamic language in its accepts() method, and returns a boolean value.

We will build on the existing org.jppf.scripting framework already uysed in the admin console. Some default varibale bindings will be provided:
  • the JPPFSystemInformation of the node being evaluated
  • the server-side or client-side SLA and metadata of the job being matched
  • the number of nodes to which the job is currently dispatched
  • a snapshot of the server statistics
For now, the choice of languages is still limited to Groovy and JavaScript, however this should be easily expandable later on, by using an SPI-based discovery mechanism instead of the current script engine factory.

#2
Comment posted by
 lolo4j
Dec 22, 21:03
trunk revision 2984
#5
Comment posted by
 lolo4j
Dec 24, 14:56
implemented in trunk revision 2986