[jira] [Closed] (VELOCITY-799) Optionally add context to itself

["Claude Brisson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/VELOCITY-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claude Brisson closed VELOCITY-799.
-----------------------------------
    Resolution: Won't Fix

Doing so would be confusing in frameworks like VelocityTools that use a ContextTool to do so. The ContextTool also provides several usefull Context introspection methods.

And it's a single line Java call to do this:
  context.put("zeContext", context);

Most frameworks using Velocity provide a way to customize the context in one way or the other.


> Optionally add context to itself
> --------------------------------
>
>                 Key: VELOCITY-799
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-799
>             Project: Velocity
>          Issue Type: Improvement
>            Reporter: Sebb
>
> 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-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org