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.
If I understand this correctly, this would be easy if only I could store the values in the validator instance, for instance during rendering, for later use in the validator. However it seems like Validator instances are shared in Tapestry, which makes this option unfeasible. This being said, my only option seems to be that when, for instance, I need values A, B and C in my validator's /isRequired()/ and /validate(Field, Void, MessageFormatter, Object)/ methods , I need to find the methods in *mycomp* that will cause the invocation of these validator methods, and push & pop the values in there. Do I understand this correctly and if so, is there an easy way to find these methods (my IDE's call hierarchy doesn't provide me with the answers)? Or, isn't there an easier way to read a component's state from within a validator that it contains? Some additional context: the custom validator is just a "Conditional Required" validator, and the outer component mycomp knows (already during rendering), whether this conditional validator should be active or not. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Reading-out-a-Component-s-formal-parameters-values-tp5680502p5682551.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
