You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/18 00:41:10 UTC
[jira] [Resolved] (TAP5-1426) Language is set to server default by
calling the root url of an app
[ https://issues.apache.org/jira/browse/TAP5-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1426.
----------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
Fixed as TAP5-1701
> Language is set to server default by calling the root url of an app
> -------------------------------------------------------------------
>
> Key: TAP5-1426
> URL: https://issues.apache.org/jira/browse/TAP5-1426
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Mxxxxx
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> http://tapestry.apache.org/tapestry5/guide/conf.html states:
> Tapestry recognizes the root URL, where the servlet path is simply "/", and renders the application page "Index", if it exists.
> If an application START_PAGE_NAME is set to index so the app runs under server/app/index.html a request to server/app/ is encoded in the server default language which may lead to nonexisting property files or wrong encoded messages. The usual routine in ComponentEventLinkEncoderImpl - decodePageRenderRequest doesn't get executed and therefore no language encoding gets set or rather it's set to the server default language. A workaround was made with setting the START_PAGE_NAME to index/thisIsJustAWorkaround (which does not exist) as this page now gets localized by Tapestry and non existing pages, get forwarded to index.html by Spring Security which does the (ugly) trick.
> Reproduction:
> Start Server in language where no properties file exist for.
> Open root url of app as described above.
> Instead of localized messages missing keys is shown.
> Tapestry Core Version 5.2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira