I realise that it's a hack but unfortunately tapestry is using MappedConfiguration<Class, Translator> so that there can only be one translator mapped per class.
Perhaps this is another argument to consider adding a MultiMappedConfiguration http://tapestry.1045711.n5.nabble.com/MultiMapConfiguration-td5714003.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Named-translators-tp5715756p5715781.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
