The application I'm working on currently uses Velocity for simple template processing; some forms, extract data, etc.
In response to trying to meet a business need of a client, it was proposed that we use Velocity basically as an engine to allow users of the system to write custom logic in the system. This include statement logic and setting values on objects passed it (which would later be persisted to a database). No actual template processing would be done, it is essentially only used to set values on an object. While it would (and in fact, does) work, it just feels horribly wrong, especially when we have another engine hooked into the system to allow custom rule writing. Am I just being overly sensitive to the use of Velocity here, or are there any other downfalls that this implementation may have that we should be aware of. Volume is supposed to be fairly low (at least as far as I've been told) and the templates would not be very complex. Thanks, Mark -- View this message in context: http://www.nabble.com/Using-Velocity-only-for-scripting-purposes-tp22935096p22935096.html Sent from the Velocity - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
