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
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
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
Михаил Слободянюк wrote
>
> Hi!
>
Hi!
Михаил Слободянюк wrote
>
> When i wrote bean display/edit block i must know state of other properties
> of object in addition to current editable.
> Why Grid, BeanEditor and BeanDisplay do not provide it possibility?
>
A good question - it would be help
