Koen Rousseau wrote : > Hmm, just a quick remark: Velocity is the View part of an MVC architecture. > That should also be reflected in the functionality of Velocity. Most of the > proposed functionality has little to do with the presentation layer. It is > the Model that needs to return the data in the correct format.
That's true from your point of view, but the tools approach (also called the pull MVC model) is a new paradigm in itself, beyond MVC concept. The main idea is to provide standard APIs to the designer. That is, the role if the controller can be quite minimized in such models. It's a personal choice. While standard MVC frameworks exhibit a cleaner separation between design and business logic, the pull model has the advandage to be much more lightweight and evolutive. > Make sure the Model returns either a > JavaBean, or a Collection of JavaBeans to the View, and you'll find Velocity > has ALL the functionality you could wish for. JavaBeans can be tools ! (even if personnaly, I find the JavaBeans too heavy... kind of pretentious... but that is subjective anyway). What is cool in the tools approach is that you can control the accessibility of standard tools from within a nice xml config file. CloD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
