Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1
    • Labels:
      None

      Description

      Follow up from JEXL-194...

      As an implementation to the extension of statement executions in JEXL we could introduce the use of annotations to each statement or block in the script, i.e.

      @synchronized(items) {for (x : items) ...}
      

      Each statement block should be allowed to have only one annotation but it would be convenient to allow the syntax

      @silent @lenient {null.tryMe()}
      

      which should be syntaxically equivalent to:

      @silent {@lenient {null.tryMe()}}
      

      From the JexlEngine point of view, each annotation could be implemented in the form of Interceptor interface, for example

      public interface Interceptor {
         public Object onExecute(JexlStatement block, String annotation, Object.. args);
      }
      

      The annotation syntax should allow for zero, one or more parameters. Those parameters should be evaluated before interceptor execution and submitted to the Interceptor.onExecute() method via args parameter.

      JexlEngine should be given a method to register annotation interceptor based on annotation name, and the one for default interceptor, which should be called before each statement execution as if @default annotation is declared in each statement in script.

      @silent {@default {...}}
      

      The JexlStatement is the proposed new interface to somehow identify the statement or block of code which may also provide some info about it's stack frame.

      public interface JexlStatement {
         public Object interpret();
      
         // ..
      }
      

      The JexlStatement.interpret() method should trigger the execution of the statement block, returning statement's result as its return value.

      In the absence of a matching interceptor corresponding to the annotation name, JexlEngine should simply ignore that, or write some diagnostic message in the log file.

      Such implementation could provide developers with excellent tool to add various checks and enhancements to scripting without pushing for new features that eventually would mess up the basic code. The JEXL-185 issue could also be dropped since tracing could be added easily via interceptors.

        Attachments

          Activity

            People

            • Assignee:
              henrib Henri Biestro
              Reporter:
              dmitri_blinov Dmitri Blinov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: