apestry upgrade from
>> 5.0.16-SNAPSHOT
>> >> > and it was working.
>> >> > Has something been modified regarding the application message catalog
>> >> or
>> >> > the localization process ? I can't find any change in the nightly
>> >> > documentati
modified regarding the application message catalog
> >> or
> >> > the localization process ? I can't find any change in the nightly
> >> > documentation ...
> >> >
> >> > Thanks in advance.
> >> >
> >> > Stephane
> >> >
> >> >
> >
;> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-
I found a bug. First entry in properties file is never used. I tried
reordering entries and the first entry never gets "translated". I used T
5.0.15, 5.0.16 and 5.0.17. This applies not only for application wide
catalog but also for page catalogs.
I am filing a bug report at https://issues.apache.
Nothing there has changed; it's still based on the filter name.
On Thu, Dec 4, 2008 at 6:02 AM, Stephane Decleire
<[EMAIL PROTECTED]> wrote:
> Since 5.0.17, my localized messages are not read anymore from the
> application message catalog.
> My application message catalog is named backoffice.prope
Since 5.0.17, my localized messages are not read anymore from the
application message catalog.
My application message catalog is named backoffice.properties because my
filter in web.xml is called backoffice and this file is located in the
WEB-INF directory as explained in tapestry localization tuto
