Java Tutorial - Java Script :
Product Selection
All of the template engines we have presented in this chapter are stellar performers; there’s no doubt about that. There are also some good template engines (such as Tapestry) that have not been presented here. Ultimately, all of the template engines we have mentioned could have a role in your development shop. The applicability of a particular template engine will probably be dependent on the needs of and features that are required by the user for a particular application. We will base our decision primarily on two factors:
Ease of use. The three template languages seem to offer the same complexity in the template languages themselves. However, Tea seems to be the most cumbersome of the three products to set up and support. Both WebMacro and Velocity are easy to set up and start using, with the edge here going to WebMacro.
Project viability. There do not seem to have been any new Tea releases in the past couple of years. Tea has also recently been moved away from its original home to SourceForge.net, which may indicate that Disney and its original creators are abandoning the product. WebMacro currently boasts five active developers and continues to release new versions. WebMacro seems to be used primarily for Web development and does not seem to have been widely used as a component in other significant open source projects. Velocity is a part of the larger Jakarta project and is used in several other visible open source projects both internal and external to the Apache group. Because of this, we think Velocity has a lead over WebMacro in project viability.
For our purposes, we have to give Velocity the win. In addition to its wide popularity as demonstrated by the number of projects that have used it as a component, we feel that the support of the Jakarta group will help to ensure that Velocity will remain compatible with other Jakarta-based products. Because Jakarta is a major provider of open source Java tools, we feel this gives the edge to Velocity.
