Hi,
Why cleanup ALL the template context after LoginAction ? In T2.3 the Turbine servlet remove the template context from the RunData after execute the LoginAction. Reading the CVS annotations, I found that Henning said that he coded in this way, to fix a bug related to session pull-tools. But with this code if the LoginAction (in my case this extends VelocityAction) put some object into the context, it isn't available in the template. The same happens with the request pull-tools, if the LoginAction modified a request tool, this modification isn't available in the template, because ALL the template context is cleaned and then rebuilded (with a "clean" request tool). So, why to break all the standard functionality of Pull-Tools+Context+Actions+Screens in the LoginAction? Why not to just remove the session pull-tools from the context, after the LoginAction, and not remove ALL the context? Any comment? Am I missing something? TIA ---------------------------------------------------------------------------- Edgar Gonz�lez Gonz�lez VALHALLA Project, s.a. Chief Technology Officer Web: www.valhallaproject.com E-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Phone: +58-212-242.4379 / 6662 / 4055 / 6475 Fax: +58-212-242.6809 "The limits of my language mean the limits of my world." Ludwig Wittgenstein ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- Edgar Gonz�lez Gonz�lez VALHALLA Project, s.a. Chief Technology Officer Web: <BLOCKED::http://www.valhallaproject.com/> www.valhallaproject.com E-mail: <BLOCKED::mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] / <BLOCKED::mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] Phone: +58-212-242.4379 / 6662 / 4055 / 6475 Fax: +58-212-242.6809 "The limits of my language mean the limits of my world." Ludwig Wittgenstein ----------------------------------------------------------------------------
