I'd like to pragmatically change the super-class's field 'clientId' so that I can get a good string value coming into processSubmission. However... AbstractField.getClientId() is final and cannot be overridden.
Rather than re-writing (or copy/pasting) AbstractField to simply provide a setClientId() method or make getClientId() non-final, I thought I might try something a bit hackish.
I've tried getting a propertyconduit (but it complains the field is readonly; as it is bound to 'componentResources.id'). I would like to try a ParameterAccess but I cannot seem to get a handle on one from inside the component (which currently extends AbstractField).
Is this what createDefaultParameterBinding() is meant for? I can't seem to figure that one out.
Is there a better way to do this? Tapestry can write to the field, so I know that it is possible in theory.
-- Robert Hailey tapestry 5.1.0.5 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
