on 8/16/01 6:12 PM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> It "seems" like all of the objects which are being #set in a template are
> being set into the Global scope context instead of the request context and
> therefore are being kept/held across requests to the server.
Now, looking at the code, this is the case and this is bad...this isn't the
way that it should work...I also see another area that is messed up, for
example:
public void preExecuteAction(RunData data)
throws Exception
{
TemplateContext context = Module.getTemplateContext(data);
data.setTemp(Turbine.CONTEXT, context);
}
If you look at Module.getTemplateContext(data), it already does a
data.setTemp(...) within the method itself.
Jason, we can't put a global context into the templates like that because
any #set references are going to be putting things into memory on the server
across requests and that is bad.
Can you fix it or do you want me to start hacking around?
Thanks,
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
