[
https://issues.apache.org/jira/browse/VELTOOLS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651931#action_12651931
]
Ezra Epstein commented on VELTOOLS-110:
---------------------------------------
Hmmm. I didn't see it as either-or. Rather one more Tool. There were a few
places (e.g., array index access, general Java operators) where I found myself
reaching for Ognl. Didn't bother to implement it - instead I extended the Java
objects that I was putting into the Velocity Context. Your call, of course. I
would just say I view it as one more option, not as something that removes the
utility of the other tools.
> 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]
