I'm starting to agree with your original suspicions that it's something to do with the "message:" binding. Under the hood, MessageBindingFactory creates a LiteralBinding which can be seen in the error message. I'm guessing you are in some byte code state where tapestry can read from the binding but can't write the property to a ThreadLocal as happens with normal properties.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Can-t-change-BeanEditForm-submitLabel-with-a-mixin-tp5716012p5716039.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
