Or you could create a new message binding prefix that uses
java.text.MessageFormat.
-Filip
Davor Hrg skrev:
I've been playing with mesage catalog,
I want to make an implementation that
will load translations from database, and
also creating components to allow adding
translations while applica
One choice is to provide your own message binding by contribute a binding
source in your AppModule.java like below.
You could use any formatter you want in there.
---
public void contributeBindingSource( MappedConfiguration configuration )
{
configuration.add( "myms
I've been playing with mesage catalog,
I want to make an implementation that
will load translations from database, and
also creating components to allow adding
translations while application is working
(this made my life easier on projects where users,
made translations on the fly while testing the
Is there some reason Tapestry chose to use 'java.util.Formatter' style
formatting as opposed to 'java.text.MessageFormat' style? The latter
seems preferable for localization, primarily because it has the 'choice'
format type. We would like to use the 'java.text.MessageFormat' style
for our applicat
