On Fri, Mar 13, 2009 at 3:25 PM, Antonio Petrelli <antonio.petre...@gmail.com> wrote: > 2009/3/13 Nathan Bubna <nbu...@gmail.com>: >> On Thu, Mar 12, 2009 at 4:14 PM, Antonio Petrelli >> <antonio.petre...@gmail.com> wrote: >>> Is there a way to solve this problem? >> >> Yes. :) But i don't know if it can be done internal to Tiles2Tool >> with the current API you have for it. I have the suspicion that if it >> had a more Velocity-ish API (rather than the tag-like one it has), >> this might not be an issue. > > The reason that Tiles2Tool has this structure is that I foresee a sort > of automatic generation of code (JSP taglib, FreeMarker template > directives, Velocity tools, etc.). I think that more Velocity-ish > methods will be added.
sounds good. >> So, i am considering adding a "page/context" scope to the Tools >> infrastructure. Or maybe try to have just one context per request? > > I discovered an easier way: using Renderable, because the "context" > parameter is connected to the current template. > I will commit this code soon. heh. very nice. Renderable is still a new toy to me, so i hadn't thought of it. > Thanks a lot! > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > For additional commands, e-mail: user-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
