Nevermind, Resolved this with field.getControlName rather than
field.getClientId.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-back-to-method-Exception-tp5712975p5713007.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
I managed to get the page to render without issue. At render it calls my
FieldValidator method and I can see the field.clientId(). However onSubmit,
the field.getClientId() becomes null. Any ideas?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-ba
Thanks Rebert for the explanation. Wasn't quite the answer I was hoping for
since I was trying to keep the backend clean, but looks as if this is the
only way to get this working dynamically. Once again, thanks.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-componen
Hi George,
The problem is with the "component:shiptoContactName" piece of the expression.
Specifying the property prefix (eg: prop:, component:, validate:, etc.) only
works at the beginning of the expression, and it is applied to the entire
expression.
The thing to do in this case is:
.tml:
Sorry, my I posted the wrong backend method in my question.
public FieldValidator getFieldValidator(Field field) {
return null;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-parameter-back-to-method-Exception-tp5712975p5712977.html
Sent from the T
