Closed GoogleCodeExporter closed 8 years ago
The problem is caused by GWT's permutation will add locale entry to
permutationProvider. So the getPermutationStrongName cannot retrieve right
strong name because of "value.size() == computedBindings.size()" is not match.
Original comment by kevn.t...@gmail.com
on 21 Mar 2013 at 10:27
If you change the default permutations you will need to build your own server
(extends the base servlet) and provide the right property providers. There is
no generic way to do this, since we can not guess in front which permutation
providers you are going to need.
If you feel there is something we can do (maybe document this better) please
let us know!
Original comment by kurka.da...@gmail.com
on 30 Mar 2013 at 9:42
Well, I agree that there is no generic way to do it for all possible
permutation providers, but there is a way to do it for i18n: you get the Locale
from the request, convert it to GwtLocale, and return the correct manifest file
(according to the user agent and locale).
This is an example that creates a different manifest file for each agent and
locale:
http://pastebin.com/JHi7NEuA
It is missing the server side servlet that will select the correct manifest
file...
Original comment by Yoav.Zibin@gmail.com
on 21 Apr 2013 at 4:12
Same problem here!
Original comment by michael....@googlemail.com
on 4 Mar 2014 at 11:35
Daniel, more than a year ago you asked:
>> If you feel there is something we can do (maybe document this better) please
let us know!
To me, this part (adding your own property providers - and which default
property providers to add or not) is not well documented yet. I guess adding an
example in the wiki would also help a lot.
In my project I have a locale property in the gwt.xml file - but not the user
agent property. I created a LocalePropertyProvider that I add in an extension
of MGWTHtml5ManifestServlet. It feels that I should not add the
UserAgentPropertyProvider, but I have tried all kind of ways to get this
working - but always get the unkown device exception...
Original comment by pdalk...@gmail.com
on 19 May 2014 at 10:17
Original issue reported on code.google.com by
kevn.t...@gmail.com
on 5 Feb 2013 at 7:17