I have an application on Tapestry 5.3.6 that is deployed to GAE 1.8.0. The problem I have seems to be appengine specific (and not necessarily tapestry specific) as I have older versions of this application running on GAE and rendering the locale specific templates normally (whereas now the older versions have the same problem).
I have some locale-specific templates (e.g. foo.tml, foo_bg.tml and foo_ru.tml). When I run the application in the local dev app server, the locale specific templates render normally. However, when I deploy the application to the appengine, the locale specific templates render the characters as question marks (???), e.g. compare http://www.zadachite.comvs http://www.zadachite.com/bg . I wonder if anyone else has run into this issue running Tapestry on GAE. A few relevant facts / attemps to fix this , so far no luck. I would appreciate any ideas/tips on how others deal w/ this (possibly when deploying to GAE), as right now my application is sunk. --------------------------------------------------------------------------------------------------------- 1. I explicitly specified the file encoding to UTF-8 in maven : <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>2.6</version> <configuration> <encoding>${project.build.sourceEncoding}</encoding> </configuration> </plugin> 2. I tried setting the file.encoding and DEFAULT_ENCODING properties, as suggested in http://stackoverflow.com/questions/11907764/is-there-a-way-to-use-utf-8-with-app-engine https://developers.google.com/appengine/docs/java/config/appconfig#System_Properties_and_Environment_Variables 3. (This seems to be the root of the problem) In my local environment, the Charset.defaultCharset() prints "UTF-8"; however, when deployed to GAE, it prints US-ASCII 4. This seems to be related to https://issues.apache.org/jira/browse/TAP5-1778 5. When retrieving values from the component messages (locale specific, e.g. foo_bg.properties), the values seem to be displayed properly (e.g. notice the menus in the example pages in the app render properly, not as question marks).
