On Jul 22, 2005, at 1:39 PM, Jamie Orchard-Hays wrote:
I don't see how this is a bug. The "value" attribute is called twice, so the second one wins. Tapestry isn't responsible for coder errors!
I'll agree to a certain extent. Clearly though, the programmer shouldn't use the same attribute twice, so providing a useful error message is key. Assuming the user somehow decided he didn't actually want the first attribute value is odd behavior.
-- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
