Separating the servlet stuff from the template engine itself seems like a good idea to me (even if it means that for compatibility reasons that there is a deprecated version around for awhile). And to me, it would be nice to see tools split up that was as well - those that can be used without servlets and those that help in a servlet based web application.
My opinion is probably slanted, as what drew me to Velocity was the template engine itself, not that it could be used in a web application (while I have since decided that I like that as well). Cort -----Original Message----- From: Tim Colson [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 4:22 PM To: 'Velocity Developers List' Subject: RE: [veltools] Proposal to move VelocityServlet from CORE into Tools > I'd be against that, because it's a pain for a new user - you would > need to get multiple things to just do baby steps... There's no harm > in leaving an example servlet in the core, Hmm. I see the new user pain stemming from trying to use the existing VelServlet. That's the reason I proposed to remove it from the core package and docs. As it sits, the newbie tries to use VelocityServlet in Tomcat and then posts "Why can't it locate my templates in WEB-INF/templates/foo???" And then somebody has to tell them to check out the Tools implementation with WebAppLoader because VelocityServlet is a bit lacking in regard to Servlet API's. I'd prefer to say, "Look at Velocity! It is JUST a [really cool] Template Engine! For using the templates in a web or Struts app, go look at the Tools project." Would help to stop the belief that Velocity Core should understand anything besides processing templates. Hah...and as one last desperate plea, there was an opinion that 'generic Tools' should not be mixed with Servlet stuff. So why should Core Template Engine be mixed with Servlet gunk. :-) -Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
