[
https://issues.apache.org/jira/browse/VELTOOLS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELTOOLS-110:
----------------------------------
Fix Version/s: (was: 2.0)
I know a bit about OGNL, but what i know leads me to see it as more similar to
Velocity itself than to the Tools used within Velocity. Do you have examples
of how you would use it within Velocity? Or how an OGNLTool would be used?
As to why VelocityContext doesn't implement Map, it just doesn't appear to be
an itch that anyone has yet found necessary to scratch. If it itches you, feel
free to post a patch to Velocity Engine's JIRA or open a thread on the dev list
or something.
> 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]
