[
http://issues.apache.org/jira/browse/VELOCITY-496?page=comments#action_12450329
]
Christoph Reck commented on VELOCITY-496:
-----------------------------------------
For completeness: the implementation should also consider that a property
access after the map access might be used:
$map.foo.bar.baz
meaning
$map.get("foo.bar") .getBaz()
So a descision is needed if this feature will be supported.
Also consider having eplicit syntaxt for a map access with a dotted key:
$map.{foo.bar}.baz and ${map.{foo.bar}.baz}schmoo
which would resolve this issue and my completeness request
> Allow periods in references secondary keys.
> -------------------------------------------
>
> Key: VELOCITY-496
> URL: http://issues.apache.org/jira/browse/VELOCITY-496
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Claude Brisson
> Priority: Minor
>
> This is a quite prospective proposal that emerged from a discussion in a
> VelocityTools JIRA issue (https://issues.apache.org/jira/browse/VELTOOLS-69).
> Its goal is to have the short syntax $map.foo.bar chek the existence of
> $map.get("foo.bar") when $map.foo is null.
> Backward compatibility is 99%, since it only breaks templates that rely on
> $map.foo.bar being an invalid reference while having foo.bar as key in map.
> The implementation doesn't look obvious, and we must ensure that there are no
> other side effects, yet this behaviour can be quite usefull when dealing with
> HTML field names that contain a period.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
