Hi all,
I am migrating an application to Tapestry 5.3. This application uses its own system to manage i18n messages (using a database to store messages). I would like to bridge its API to t5's Messages API, so I can transparently use the "message" binding with keys from the old system. Unfortunately, I did not find a easy way to achieve this (this only way to contribute the ComponentMessageSource is to provide extra Resources with a file semantic). Any idea? Best regards Guillaume
