I'm seeing an issue with the new Hidden field component in 5.1.0.2. I've written a ValueEncoder to translate between string and java.sql.Date, but this throws a class cast exception when used as the encoder parameter for the hidden field.
If I use a regular TextField component and use a ValueTranslator, then this works without problem. The question is, why does Hidden field use an encoder, when TextField uses a translator? Perhaps there should be some consistency here. -- View this message in context: http://www.nabble.com/Hidden-field-encoder-problem-tp22919903p22919903.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
