Thanks for the tip!
Having read the documentation on Environmentals, it looks to me like I have
to push the required values in the outer component in a method that will
lead to the invocation of the validator method where I need them, and pop
the values, for instance, when this method returns.
I
In that case I'd use an Environmental. Have t:mycomp push an object into the
environment and the validator can access it. If you don't want do modify
t:mycomp you could use a mixin to push the object into the environment.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Read
Actually, the validator will be applied to a component that's one level
deeper than my custom component (for instance: ; where
customvalidator requires the values of a and b).
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reading-out-a-Component-s-formal-parameters-values
Actually, the validator will be applied to a component that's one level
deeper than my custom component (for instance: ; where
customvalidator requires the values of a and b).
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reading-out-a-Component-s-formal-parameters-values
If you are just writing a validator for one specific component and not a
general purpose one you can use a mixin. They can have access to the
component parameters via @BindParameter
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reading-out-a-Component-s-formal-parameters-
