Jesse,
I just added:
meta key=org.apache.tapestry.accepted-locales value=en/
to my .applicaiton file.
This solves it for me, and is most likely an good improvement for my
application for other reasons.
Thanks, Paul.
Jesse Kuhnert wrote:
You can try replacing the default version of
Anyone?
Paul Stanton wrote:
Hi,
I've just installed 4.1.2 for the first time and run up my application
(previously tested under 4.1.1). I did this simply by replacing my
existing jars with the new versions (I don't use maven) so I've
probably brought this on myself ;)
I get the following
I had opened up a jira for this:
https://issues.apache.org/jira/browse/TAPESTRY-1551
I'm not exactly sure if there's a way to tell dojo which locales exist
in the server so as not to do those requests...
The only hack i can offer you is to create those 2 classpath entries
yourself, by copying
Additionally, take a look at
http://tapestry.apache.org/tapestry4.1/usersguide/localization.html#localization.accepted-locales
It's always a good idea to limit those to the ones your app truly supports
andyhot wrote:
I had opened up a jira for this:
Thanks, looks like it missed the 4.1.2 boat :(
andyhot wrote:
Additionally, take a look at
http://tapestry.apache.org/tapestry4.1/usersguide/localization.html#localization.accepted-locales
It's always a good idea to limit those to the ones your app truly
supports
andyhot wrote:
I had
Hi,
I've just installed 4.1.2 for the first time and run up my application
(previously tested under 4.1.1). I did this simply by replacing my
existing jars with the new versions (I don't use maven) so I've probably
brought this on myself ;)
I get the following warnings, the files can be