--- Terry Steichen <[EMAIL PROTECTED]> wrote: > I see what I think is a potential problem with using Velocity in a > product (commercial or open-source) designed to be used and extended > by > others. While VTL makes extension by users about as easy as it gets, > if > you also use VTL for the core parts of the product, it is possible > that > a user will inadvertently mess them up, making the product fail to > properly operate. This kind of customer support problem might be > very, > very difficult to track down.
Pithy answer: any customization feature powerful enough to be useful, will be powerful enough to create the problem you see. Therefore, if you want customization features that powerful, you need to build in debugging and error catching features to minimize the problems. That is true with Velocity or with anything else. The important thing is to understand the problem from the beginning, and design in those support features from the beginning. BTW: I'm assuing that you want people to customize their templates, so the 'templates in Jar' stuff will not help you. You are afraid that they will make a mistake while customizing, and that your system will pay the price for that mistake. Joshua Levy __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
