"Kimpton,C (Chris)" wrote:
>
> Hi,
>
> >
> > The Velocity integration I'm doing is to two fold:
> > - write a VelocityPortletControl (adapted from Roberto
> > VTLPortletControl) and
> > reimplement the base controls woth velocity templates
> > (done, but uncommitted)
> > - write a VelocityPortlet that enables you to easily
> > implement a Velocity based
> > portlet (about 60% done but depends on the new PSML persistence...)
> >
>
> Sounds great.
>
> Although it was easier than I thought it would be to use velocity in a
> portlet.
>
> I enabled the velocity service in the TR.props file.
>
> In my portlet, I just create/populate a context, get the template, merge
> them and pass out the result as a clear element.
>
Exactly. The VelocityPortlet does just that except that it delegates context
populating to an Action (through a std name mapping convention) and has a
smart template selection.
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
