> Isn't the controller going to drop whatever you've placed in
> the context
> after the action is run?
>
> I haven't looked at the code for TurbineVelocity but it looks
> like the
> VelocityPortletController uses the getContext() method which
> is getting a
> new (blank) context object.
>
>
> public class VelocityPortletController extends
> AbstractPortletController {
> public ConcreteElement getContent( RunData rundata )
> {
> // create a blank context and with all the global application
> // Pull Tools inside
> Context context = TurbineVelocity.getContext();
>
> context.put( "data", rundata );
> context.put( "controller", this );
> ....
>
Yes, that's 'how', but not 'why'.
I was under the impression that there should only be one context, the
'Velocity Context'.
It confused me to find out there are more than one. Just wanted to know
why it was implemented this way.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
