Sony Joseph wrote:
> Hi,
>
> When would one use VelocityPortlet vs TurbineScreenPortlet. I am using
> VelocityPortlet and set the template to say 'Welcome' and I also define a
> screen class called welcome. The screen class doesn't get invoked ( which I
> thought was the default behaviour of the TurbineVelocitySrevice).
>
The TurbineScreenPortlet is a demonstration of how you could try to include
a normal Turbine "push" screen and show this as a portlet. It works but there
are a lot of issues to consider that make this solution less than optimal IMO.
(the main one that the TurbinePortlet *must not* try to change the layout/template
etc... because that will mess with the Jetspeed engine as such).
Now, VelocityPortlet is just a Portlet that allows you to associate one or
several velocity Portlets with one action that is used to populate content
on demand. You can not use it as a "Turbine application front-end" directly
but if you have a modern Turbine app (pull + template) you can write
a Portlet view of this app with the VelocityPortlet in a few seconds...
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
