Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-27 Thread Lance Java
I agree, I wanted to do this "the tapestry way" via an Environmental but was forced to use a request attribute (ie "the struts way"). I'd like to understand why the cloak/decloak was introduced. -- View this message in context: http://tapestry.1045711.n5.nabble.com/5-4-alpha-2-Environment-cloak

Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-26 Thread Massimo Lusetti
On Fri, Jan 25, 2013 at 9:46 AM, Lance Java wrote: Thanks for your help guys, are you convinced that the cloaking introduced in > 5.3 is a good idea? Isn't the whole stuff of cloaking/decloaking that isn't a good idea... Is knowing how to use well that it still unsatisfactory. I find the Environ

Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-25 Thread Lance Java
I was considering a thread-local, I'd totally forgotten about request attributes... how retro!!! Thanks for your help guys, are you convinced that the cloaking introduced in 5.3 is a good idea? -- View this message in context: http://tapestry.1045711.n5.nabble.com/5-4-alpha-2-Environment-cloake

Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-24 Thread Howard Lewis Ship
You could instead attach the object as a Request attribute; that will carry over. Kind of "old school". Or the value could simply be stored in a mutable property of a per-thread service. On Thu, Jan 24, 2013 at 2:54 PM, Lance Java wrote: > Hmm... well... far from "leaking" from the action to th

Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-24 Thread Lance Java
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 r

Re: [5.4-alpha-2] Environment cloaked during ajax component event

2013-01-24 Thread Steve Eynon
This came in around T5.3, I believe the cloak / de-cloak was put in for Ajax requests so the environment used in the action phase didn't leak into the render phase. Steve. On 25 January 2013 01:31, Lance Java wrote: > Considering the simplified example below, can someone please tell me why the >

[5.4-alpha-2] Environment cloaked during ajax component event

2013-01-24 Thread Lance Java
Considering the simplified example below, can someone please tell me why the environmental peekable for a page render request but not peekable for an ajax event? Upon debugging, I have found that if I decloak() the environment, I can then peek() the model. Page.tml == MyComponent.tml ==