[
https://issues.apache.org/jira/browse/VELTOOLS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651911#action_12651911
]
Adrian Tarau commented on VELTOOLS-110:
---------------------------------------
There is another project which is similar with OGNL, but it seems it performs
better : http://mvel.codehaus.org/Home
However, the main purpose of those libraries is to provide an "expression
language" library and not a template library. Most of the time it is used to
evaluate dynamically expressions and return a value(object) and not to generate
content. Even if they will provide in the end a template functionality on top
of their expression language evaluator, it is not a project dedicated to
provide a template engine and only that. Sooner or later these projects may
take a turn and drop/change/deprecate their support for the template engine. I
agree, Velocity could borrow some of their functionality, but I don't think it
makes sense to merge a tool like Velocity(a template engine) with a tool like
OGNL or MVL(expression language).
"MVEL is a powerful expression language for Java-based applications. It
provides a plethora of features and is suited for everything from the smallest
property binding and extraction, to full blown scripts"
"OGNL stands for Object-Graph Navigation Language; it is an expression language
for getting and setting properties of Java objects. You use the same expression
for both getting and setting the value of a property. "
> 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]
