[
https://issues.apache.org/jira/browse/JEXL-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitri Blinov updated JEXL-185:
-------------------------------
Description:
Since the rising complexity of the JEXL scripts makes it easier to write
sophisticated scripts, and harder to debug overall script evaluation, it would
be helpful to provide some way to trace individual statements execution within
the script by a callback interface.
Callback could be applied to JEXL engine as a whole, or to Script.executeScript
method as an additional parameter for example.
Callback interface should contain a method which should be invoked by JEXL on
completion of individual statement. Method parameters should contain such
values as DebugInfo (start..end statement position within the script),
statement execution result or exception (which in silent mode may be
swallowed), initial context, and possibly a stack frame to be able to peep into
local variables.
was:
Since the rising complexity of the JEXL scripts makes it easier to write
sophisticated scripts, and harder to debug overall script evaluation, it would
be helpful to provide some way to trace individual statements execution within
the script by a callback interface.
Callback could be applied to JEXL engine as a whole, or to Script.executeScript
method as an additional parameter for example.
Callback interface should contain a method which should be invoked be JEXL on
completion of individual statement. Method parameters should contain such
values as DebugInfo (start..end statement position within the script),
statement execution result or exception (which in silent mode may be
swallowed), initial context, and possibly a stack frame to be able to peep into
local variables.
> Ability to trace execution of script statements
> -----------------------------------------------
>
> Key: JEXL-185
> URL: https://issues.apache.org/jira/browse/JEXL-185
> Project: Commons JEXL
> Issue Type: New Feature
> Affects Versions: 3.0
> Reporter: Dmitri Blinov
> Priority: Minor
>
> Since the rising complexity of the JEXL scripts makes it easier to write
> sophisticated scripts, and harder to debug overall script evaluation, it
> would be helpful to provide some way to trace individual statements execution
> within the script by a callback interface.
> Callback could be applied to JEXL engine as a whole, or to
> Script.executeScript method as an additional parameter for example.
> Callback interface should contain a method which should be invoked by JEXL on
> completion of individual statement. Method parameters should contain such
> values as DebugInfo (start..end statement position within the script),
> statement execution result or exception (which in silent mode may be
> swallowed), initial context, and possibly a stack frame to be able to peep
> into local variables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
