JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-514  -  Lighter syntax for scripted property values
Posted Aug 29, 2017 - updated Aug 30, 2017
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
    Enhancement
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Configuration
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
Examples of current syntax:
# following two are equivalent
my.prop1 = $script:javascript:inline{ 1 + 2 }$
my.prop2 = $script{ 1 + 2 }$
 
my.prop1 = $script:groovy:file{ /home/me/script.groovy }$
my.prop1 = $script:javascript:url{ file:///home/me/script.js }$
This is a bit cumbersome. We propose to relax the syntactic constraints and allow using 'S' or 's' instead of 'script', and only specifying the first character of each possible script source type ('u' or 'U' for url etc...)

#3
Comment posted by
 lolo4j
Aug 30, 06:42
Implemented in trunk revision 4598