I'm lost at the issues here. Can someone please summarize the issues or point out some stuff in the archives? I'm very confused. I don't see how ToolLoader mixes up the model and controller into the view.
I'm only looking at this for the point of using the VelocityViewServlet, which I like a lot. This means I don't have to create a class for every template file I create. This seems like a big advantage, but Jon seems to be implying that part of the VelocityViewServlet -- ToolLoader is flawed because it mixes the model and the controller. Plus, it has already been done better in Turbine. Third, he also seems to be the implying that this is not a Pull method, which I thought it was. I hope I've actually summarized Jon's issues. If not, please please feel free to correct me. My questions are: . What if I don't want to use Turbine? I may want to use Struts or an Oracle framework, but I don't want to give up using Pull method with Velocity. . Can some explain why ToolLoader is bad? What is good? . Isn't this a Pull method? . If Turbine has indeed done this already, can we refactor functionally out so it doesn't depend on Turbine? Thanks, Jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
