[ 
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636354#action_12636354
 ] 

Byron Foster commented on VELOCITY-618:
---------------------------------------

If VELOCITY-619 is not accepted then a possible change to this patch is to 
allow undefined variables in the one case of:

#if ($foo)

As discussed in VELOCITY-619, creating a special case sometimes leads to 
behavior confusion, but it may work out well in this case.

> Strict property and method references
> -------------------------------------
>
>                 Key: VELOCITY-618
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-618
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>            Reporter: Byron Foster
>             Fix For: 1.5.1, 1.6
>
>         Attachments: strictPropertyAndVariable_2.patch
>
>
> The given patch against trunk adds a new option 'runtime.references.strict'.  
> When set to true, invalid property references will throw a 
> InvalidMethodException.  For example $foo.bar will throw an exception if the 
> object contained in $foo has no such property as bar.  Any kind of reference 
> to bar will cause an exception including:
> #if(#foo.bar)
> #set($foo.bar = "junk")
> #set($foo.getBar())
> etc...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to