You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Quintin Siebers (JIRA)" <de...@velocity.apache.org> on 2011/04/15 14:21:06 UTC
[jira] [Updated] (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 ]
Quintin Siebers updated VELOCITY-800:
-------------------------------------
Attachment: SubsequentInvalidReferenceEventHandlerTest.java
> 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
> Priority: Minor
> Labels: event, invalid, method, reference, resolve
> Attachments: SubsequentInvalidReferenceEventHandlerTest.java
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org