You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Claude Brisson (JIRA)" <ji...@apache.org> on 2018/10/08 19:52:00 UTC
[jira] [Resolved] (VELOCITY-800) Subsequent invalid references
cannot be resolved by InvalidReferenceEventHandler.invalidGetMethod
[ https://issues.apache.org/jira/browse/VELOCITY-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-800.
-------------------------------------
Resolution: Won't Fix
Assignee: Claude Brisson
To answer from the user in two years.
> Subsequent invalid references cannot be resolved by InvalidReferenceEventHandler.invalidGetMethod
> -------------------------------------------------------------------------------------------------
>
> Key: VELOCITY-800
> URL: https://issues.apache.org/jira/browse/VELOCITY-800
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7
> Reporter: Quintin Siebers
> Assignee: Claude Brisson
> Priority: Minor
> Labels: event, invalid, method, reference, resolve
> Attachments: SubsequentInvalidReferenceEventHandlerTest.java, VELOCITY-800.patch
>
>
> If $foo is a java.lang.String and a template tried to do $foo.bar, one can use an InvalidReferenceEventHandler to resolve bar into a value. However, if the template tries to do $foo.bar.baz, the last part cannot be resolved using an InvalidReferenceEventHandler. I'll attach an example test case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org