Hey,
I'm now using my own implementation of AbstractMessages as I described
in my previous mail. I do exactly the same as in MessagesImpl. The only
difference is that I add something to the baseName argument used in
ResourceBundle.getBundle(baseName, ...).
The selecting of the correct resour
On 12/08/15 17:36, Thiago H de Paula Figueiredo wrote:
On Wed, 12 Aug 2015 11:37:29 -0300, Nathan Quirynen
wrote:
Hi Thiago,
Hi!
That's actually a clever solution, but seems a bit "hacky" and I'm
not sure how it will also use the usual Index(_en).properties files?
If you create a Locale
On Wed, 12 Aug 2015 11:37:29 -0300, Nathan Quirynen
wrote:
Hi Thiago,
Hi!
That's actually a clever solution, but seems a bit "hacky" and I'm not
sure how it will also use the usual Index(_en).properties files?
If you create a Locale("en", "120) and a message isn't found in
Index_en_1
Hi Thiago,
That's actually a clever solution, but seems a bit "hacky" and I'm not
sure how it will also use the usual Index(_en).properties files?
I solved it at the moment with adding a new binding prefix where i pass
the key and property value like following:
${messagebasedonpropertyvalue:
On Tue, 11 Aug 2015 03:29:13 -0300, Nathan Quirynen
wrote:
So I want to have the usual properties file for the page and besides
this for each possible value of a property an extra properties files in
which specific localized messages are located.
So for example an Index page it can have the
Hmm yeah kind of..
So I want to have the usual properties file for the page and besides
this for each possible value of a property an extra properties files in
which specific localized messages are located.
So for example an Index page it can have the following:
- Index.properties
- Index_en
Sorry Nathan I do not understand: do you want to spread properties belonging to
one particular page accross multiple property files?
Jens
Von meinem iPhone gesendet
> Am 10.08.2015 um 09:08 schrieb Nathan Quirynen :
>
> Hi,
>
> I have in some pages/components in my Tapestry (5.3.7) applicatio
Hi,
I have in some pages/components in my Tapestry (5.3.7) application the
need to have localized messages based on some property value.
Simplified example:
Class SomeClass {
String code;
}
In the page I have then a property of type SomeClass and based on this
value I need different loc