Yup, I avoided that code because I'd like the customcomponent to be flexible, not requiring a specific type of Field in its body, or a specific name for that Field.
In the meanwhile, I've been able to get the field reference in the custom component as follows: <t:mycomponent paramForField="component:fieldID"> <t:textfield t:id="fieldID" t:validate="var:validators" /> </t:mycomponent> This works , but: apparently tapestry makes an attempt to resolve used render variable when the form is submitted, too, and this time, it makes this attempt before mycomponent's setupRender() has executed. As a result, I get the following error upon form submission: ERROR org.apache.tapestry5.ioc.Registry - Failure reading parameter 'validate' of component MyPage:fieldID: Component MyPage does not contain a stored render variable with name 'validators'. Stored render variables: (none). Any ideas on this? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Is-it-possible-to-add-Field-validators-at-render-time-tp5682920p5685389.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
