Hi all I am thinking about new features for Velocity Tools. One can be included into 2.1 version: JSP tag library inclusion in Velocity templates. I think this would be an interesting feature, because there is a lot of tag libraries out there. In particular what I love much: DisplayTag. Including JSP taglibs is a very useful feature of Freemarker and Velocity is well behind it. I am thinking of implementing it using directives (not tools) because tools do not have body. I will start working on it at once in the trunk, stop me at any time and I will revert the job if you don't want it.
About something in a distant future, we can remove the dependency on servlets technology for Velocity Tools. What I've been doing in Tiles sandbox is extracting an API and a series of technology-supporting modules to abstract the concept of "request". You can see the result here: http://svn.apache.org/repos/asf/tiles/sandbox/trunk/tiles-request/ This can be useful for Velocity Tools to use any technology that implements this API (currently servlets, portlets, JSP, Velocity and Freemarker). If Velocity adopts this library, it can work, for example, under a portlet environment without using a separate servlet. This library works well in the sandboxed version of Tiles, the probable Tiles 3. Moreover, this tiles-request library is used by another subproject, "tiles-autotag" to generate JSP tags, Velocity directives and Freemarker directive models starting from simple classes with an "execute" method. Again, this works in sandboxed Tiles: http://svn.apache.org/repos/asf/tiles/sandbox/trunk/tiles-autotag/ One idea that today has come to my mind is to move this library as a subproject of Velocity, since it uses Velocity intensively to generate tags. Thoughts? Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
