[
https://issues.apache.org/jira/browse/VELTOOLS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652039#action_12652039
]
Nathan Bubna commented on VELTOOLS-110:
---------------------------------------
Well, with Velocity 1.6, you can now treat arrays like fixed-length lists and
use get(int) to access them, and i don't think all Java operators belong in a
template-language.
And you're right, it could be just one more option, but it would also be one
more option to maintain and support and one more dependency to add. At this
point, i don't think the redundancy is worth the cost, especially not having
seen any convincing examples of how such a tool would be used.
> An OGNL Tool, perhaps
> ---------------------
>
> Key: VELTOOLS-110
> URL: https://issues.apache.org/jira/browse/VELTOOLS-110
> Project: Velocity Tools
> Issue Type: Improvement
> Components: GenericTools
> Affects Versions: 2.0
> Reporter: Ezra Epstein
> Priority: Minor
>
> I've been using a combination of the Velocity Tools and it occurred to me
> that much of the functionality is available via OGNL and so I was thinking
> about writing an OGNL tool. Then it occurred to me that, perhaps, the
> V-Tools team hadn't yet checked out OGNL, so I'm dropping this note to
> mention it. Do check it out. OGNL with the V Context as the root "this"
> node, would be a very powerful tool.
> While on the subject of integrating with other things, I always wondered why
> the VelocityContext doesn't implement the java.util.Map interface. I know
> that's part of the Velocity project not tools, but it's a curiosity for me.
--
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]
