velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Bubna (JIRA)" <>
Subject [jira] Commented: (VELOCITY-618) Strict property and method references
Date Fri, 10 Oct 2008 03:18:47 GMT


Nathan Bubna commented on VELOCITY-618:

Yeah, i know very well how bad it is.  But it's been this way a long time and this upcoming
release is still just a minor version one.   And yeah, i know about the \$alt problem.  This
is why i essentially never use \ for escaping.  It long ago became second nature to just use
${esc.d}alt (since i pretty much always have VelocityTools available).  Anyway, we can take
the escaping discussion over to VELOCITY-623.

I'll try and get the rest of this strict mode stuff in shortly (sans the escaping part).

> Strict property and method references
> -------------------------------------
>                 Key: VELOCITY-618
>                 URL:
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>            Reporter: Byron Foster
>             Fix For: 1.5.1, 1.6
>         Attachments: MacroAndVarEscape.patch, strictPropertyAndVariable_3.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 $
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(
> #set($ = "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:
For additional commands, e-mail:

View raw message