Well, you can read the field after the component logic sets it. I often add package-private getters and setters to facilitate testing.
On Dec 1, 2007 2:34 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > > > > On 12/1/07 5:25 PM, in article > [EMAIL PROTECTED], "Howard Lewis > Ship" <[EMAIL PROTECTED]> wrote: > > > For unit testing, you don't ... you just let the parameters act like > > normal fields. > > Hmm . . . Okay, but how do you test that a component has actually modified > the value? > > E.g., I was looking at DateField for TAPESTRY-1893 and processSubmission() > overwrites the existing reference. So, I can't even check that the value I > had originally has been changed, because it will not have been. I was > hoping being able to set up a binding would allow me to do this. > > -- > > Kevin Menard > Servprise International, Inc. > Remote reboot & power control for network equipment > www.servprise.com +1 508.892.3823 x308 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship TWD Consulting, Inc. Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
