Thanks for informing me of that. I was completely unaware of this behavior and was able to clean up some code. I do believe I'm still going to need to the value encoder for my custom component, so would my code sample below work?
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Using-coposite-key-with-value-encoder-tp5519520p5519711.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