AppEngine Plugin

Google AppEngine i18n issue (unable to read messages.properties on GAE)

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Google AppEngine (SDK 1.3.0)

Description

Hi,

I've discovered that for what ever properties that I had entered into message.properties under /WEB-INF/grails-app/i18n/ could not be read after deploying to Google AppEngine.

This issue doesn't exist while testing on development environment. But after deploying to GAE, even if I tried to edit the appengine-web.xml and include the

<resource-files>
<include path="/WEB-INF/grails-app/i18n/**.properties" />
</resource-files>

it doesn't seem to work.

I believe a fix or a work around is needed.

Thank you very much for the effort.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brendan Sibre added a comment -

I had this problem after upgrading the plugin with an application that used to work.

Show
Brendan Sibre added a comment - I had this problem after upgrading the plugin with an application that used to work.
Hide
Permalink
Christian Klocker added a comment -

seems to be a problem with configuration-generation inside the app-engine plugin. as a result messagesource.basenames is empty when deployed to gae. i also noticed that a command like "grails app-engine package" runs in environment "development" - maybe that causes the problem?

i attach my bootstrap.groovy as a possible workaround.

to use it one needs to set the environment somehow:

  1. grails -Dgrails.env=production app-engine package
  2. appcfg.sh update ./target/war
Show
Christian Klocker added a comment - seems to be a problem with configuration-generation inside the app-engine plugin. as a result messagesource.basenames is empty when deployed to gae. i also noticed that a command like "grails app-engine package" runs in environment "development" - maybe that causes the problem? i attach my bootstrap.groovy as a possible workaround. to use it one needs to set the environment somehow:
  1. grails -Dgrails.env=production app-engine package
  2. appcfg.sh update ./target/war
Hide
Permalink
Christian Klocker added a comment -

workaraound

Show
Christian Klocker added a comment - workaraound
Hide
Permalink
Blake Barnes added a comment -

Hi Graeme-is there any update on this issue? Would be great to get a fix for it so that I don't have to apply the workaround on every new Grails AppEngine project I start. Thanks!

Show
Blake Barnes added a comment - Hi Graeme-is there any update on this issue? Would be great to get a fix for it so that I don't have to apply the workaround on every new Grails AppEngine project I start. Thanks!

People

  • Assignee:
    Unassigned
    Reporter:
    Max Lam
Vote (8)
Watch (8)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.