You are right ... more attention should have been given to the change in API, as it is in a public (not internal) package.
On Fri, Nov 4, 2011 at 6:18 AM, Serge Eby <[email protected]> wrote: > Hi, > > I noticed that the constructor for EnumValueEncoder was changed in T5.3 to > address some issues. > Although more flexible, It feels like this is something that should be > transparently handled by the framework. We now need more code (i.e inject > TypeCoercer) to use this feature. > Anyway, I think this change needs to be added to the breaking changes > section in the release notes. > > My 2c. > > > /Serge > > -- > View this message in context: > http://tapestry-developers.221625.n2.nabble.com/EnumValueEncoder-in-T5-3-tp6962704p6962704.html > Sent from the Tapestry Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
