DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17086>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17086 Velocity is lacking in many points to be a powerful template engine. Summary: Velocity is lacking in many points to be a powerful template engine. Product: Velocity Version: 1.3-rc1 Platform: All OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Testing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
