I like the idea a lot because i suspect it will likely make it easier for me to integrate Tiles without worrying about JSP specific things creeping into the core of Tiles.
However, we then must ask the question of whether we're going to allow modules for other template engines too? I don't think we have to answer yes to that, though. JSP, for all its problems, is the "standard" so it is easy to say we will only maintain support for Tiles+JSP here. Then we can leave Tiles+Velocity or Tiles+Freemarker to be developed elsewhere. As the VelocityTools lead, i really don't care much either way. But i am +1 for adding a module for JSP support, just to encourage cleaner, less JSP specific code. On 1/29/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Hi Just a question: do you think that adding a module for JSP support could be useful? And if your answer is yes, do you think that separating the JSP support could be a good step? What I have in mind is that supporting JSP is like supporting any other templating language. Before making any change I would like some feedback. Thoughts? Antonio
