[
https://issues.apache.org/jira/browse/VELOCITY-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383115#comment-15383115
]
Sergiu Dumitriu edited comment on VELOCITY-799 at 7/18/16 9:32 PM:
-------------------------------------------------------------------
I'm not sure, but I think jsr233 (or whatever the name of the java scripting
API) actually requires that the context is available under the {{context}}
binding/variable.
was (Author: sdumitriu):
I'm not sure, but I think jsr233 (or whatever the bame of the java scripting
API) actually requires that the context is available under the {{context}}
binding/variable.
> Optionally add context to itself
> --------------------------------
>
> Key: VELOCITY-799
> URL: https://issues.apache.org/jira/browse/VELOCITY-799
> Project: Velocity
> Issue Type: Improvement
> Reporter: Sebb
> Assignee: Claude Brisson
> Fix For: 2.x
>
>
> For debugging scripts, it would sometimes be useful to have access to the
> context within a VM script.
> For example, one could then print out all the variables that are defined in
> the context.
> The suggestion is to enable this via a properties file or a system property.
> If the property is defined, its value would be used as the name of the
> variable holding the context.
> e.g. -Dvelocity.context.variable=ctx
> Obviously feel free to choose a better property name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
