[VELOCITY-142] Velocity is lacking in many points to be a powerful template engine.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 1.3-rc1
• Component/s: Testing
• Environment: Operating System: other; Platform: All
• Bugzilla Id: 17086
• Assignee: Unassigned
• Reporter: Colbert Philippe
• Created: 15/Feb/03 02:10
• Updated: 11/Feb/11 11:23
• Resolved: 13/Sep/05 12:45

Description

I am currently attempting to use Velocity to generate various codes. At first
look, Velocity looks like the ultimate template engine. However, when you put
Velocity to the test, you realize that there are key features missing. I list
some of those features below. The missing features are related to the Velocity
language. The language is missing many features usually found in modern script
languages like JScript, Perl, Python..etc. I would suggest to use a language
like Rhino (JScript engine written in Java) as a language engine for Velocity.
This would overcome all the problems with the current version of Velocity.

Here is a list of problems with Velocity language.
1 - There is no variable scoping. This is a problem because it prevents proper
encapsulation. One cannot write fully modular macros or functions. Global
variables are overwriting each other.

2 - Velocity does not support Object Orientation. All modern scripting
languages support OO.

Regards,
Colbert Philippe