The problem is, if using the action service, a form component may render as part of the rewind cycle, but (because the form it is wrapped by is not itself rewinding) neither read nor write any of its parameters.
I'd need to externalize more of that logic, out from Form and TextField and company ... add more layers of declaration not just about the use of parameters, but about the use of the component as a whole. I haven't had a flash of insight on that, however. I'm sorry I haven't looked at your validator yet. ----- Original Message ----- From: "Mind Bridge" <[EMAIL PROTECTED]> To: "Howard Lewis" <[EMAIL PROTECTED]> Sent: Saturday, May 25, 2002 12:45 PM Subject: Validator > > Hi Howard, > > I was wondering whether you've had a chance to have a look at the Validator? (I have given it to a number of people, and they seem to be happy with it and find it useful. Nevertheless, your opinion matters a lot :-) > > Unfortunately, I am quite busy at my day job at the moment (finishing a project with my team at the moment), so I have only a little spare time. > > Btw, the changes to the component parameter definition/behaviour are excellent. Have you reached any conclusions on the usefulness of the alternative modes (other than IN and CUSTOM)? > > All the best, > > -mb > > > > > > --------------------------------- > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
