Nope, this is a bug that may require a non-backwards compatible fix. There's a conflict between getting at translators by explicit name, or by best match (by property type). The current implementation gives the latter priority and even that isn't very cool, because it lacks an override capability.
I believe the correct version will be a MappedConfiguration<String,Translator> so that you identify the translator by name for override purposes. Have you added an issue for this? On Wed, Oct 7, 2009 at 10:32 AM, Bryan Lewis <jbryanle...@gmail.com> wrote: > Hi. (I just said that so I could get one of Thiago's Hi's. :-) > > I've upgraded from Tapestry 5.0.18 to 5.1.0.5. I had been postponing it for > months because of my past experiences with upgrades from 3 to 4 to 4.1 to 5, > but this time it went very smoothly. I changed the version string in my pom > and let the maven plugin do its thing... a minute later everything was > working. Except for the loop encoder change that the release notes warned me > about, not bad at all. > > However, I had written my own BigDecimalTranslator in the previous version, > to format money values as currency. (I use the BigDecimal type only for > currency fields.) The new version has added its own BigDecimalTranslator. > Is there a way to override it with my own? I've searched the > list/blogs/jiras and got my hopes up with the OrderedConfiguration, but that > doesn't seem to work, or I'm missing something. Tapestry insists on calling > my contributeTranslatorSource() with an unorderd Configuration. > > Thanks! > Bryan Lewis > -- 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: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
