Re: Current Bean in Environment

2012-02-15 Thread Mihail Slobodyanuk
Thanks! It's good resolve. 2012/2/14 Alejandro Scandroli > I do something similar using a mixin. > Take a look at Tynamos's BeanModelAdvisor [1] > > TynamoBeanContext.getObject always returns the current iterated item > based on the container's iterator property name (in this case: "row"). > > I

Re: Current Bean in Environment

2012-02-14 Thread Alejandro Scandroli
I do something similar using a mixin. Take a look at Tynamos's BeanModelAdvisor [1] TynamoBeanContext.getObject always returns the current iterated item based on the container's iterator property name (in this case: "row"). I hope it helps. Alejandro. [1] http://svn.codehaus.org/tynamo/trunk/ta

Re: Current Bean in Environment

2012-02-13 Thread Михаил Слободянюк
2012/2/13 derkoe > A workaround could be to create your own context and push the object to the > Environment in BeginRender of your enclosing component. > Or you could use the BeanValidationContext but then you have to add your > object as validate to the Form. > In the case if Grid Context must

Re: Current Bean in Environment

2012-02-13 Thread derkoe
nContext but then you have to add your object as validate to the Form. Михаил Слободянюк wrote > > Mihail. > Christian -- View this message in context: http://tapestry.1045711.n5.nabble.com/Current-Bean-in-Environment-tp5476313p5479391.html Sent from the Tapestry - U