Hmm... well... far from "leaking" from the action to the render. I'm explicitly setting an environmental with the requirement that it's available in the render.
Is there a solution to this? I think it's pretty normal to want an environmental available in normal render and an ajax component event render. -- View this message in context: http://tapestry.1045711.n5.nabble.com/5-4-alpha-2-Environment-cloaked-during-ajax-component-event-tp5719496p5719502.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
