[
https://issues.apache.org/jira/browse/VELOCITY-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850560#action_12850560
]
Nathan Bubna commented on VELOCITY-758:
---------------------------------------
On second thought, i like the event handler support for null meaning don't
render. So we just log the null reference and blockinput. I do still want to
give the event handler a shot at null values.
> Include line number in message "#parse() null argument"
> -------------------------------------------------------
>
> Key: VELOCITY-758
> URL: https://issues.apache.org/jira/browse/VELOCITY-758
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6.2
> Reporter: Edy Hinzen
> Priority: Trivial
> Attachments: velocity-758.patch
>
>
> Assume the following scenarios:
> Scenario A)
> A template has the following line:
> #parse("never-found-template.vm")
> Scenario B)
> A template has the following line:
> #parse($nonsense)
> Assume further, that neither the "never-found-template.vm" is present nor the
> variable "$nonsense" is set.
> In scenario A) the log reports "#parse(): cannot find template
> 'never-found-template.vm', called from template ... at (1, 1)"
> In scenario B) the log says "#parse() null argument"
> Problem:
> In scenario B), having multiple nested #parse-Statements, it's hard to find
> the error finally.
> Sugestion / Feature request:
> Include source information and line numbers when reporting "#parse() null
> argument" - analogous to scenario A)
> Thanks and kind regards
> Edy Hinzen
--
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]
