[
https://issues.apache.org/jira/browse/WW-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285839#comment-13285839
]
JB edited comment on WW-3057 at 5/30/12 5:36 PM:
-------------------------------------------------
I put together a test project using the Maven Struts 2 Blank Archetype and
configured it appropriately for Struts 2 version 2.0.9. I successfully
deployed and ran the application on both Tomcat 6.x and 7.x.
I am unable to put the load on the application that the Reporter mentions;
however I am able to exercise the tags mentioned, and report that I am able to
display the associated text -- and not keys -- in every instance.
I recommend this issue be closed unless additional information is introduced to
support that the bug exists.
was (Author: jeffblack360):
I put together a test project using the Maven Struts 2 Blank Archetype and
configured appropriately for Struts 2 version 2.0.9. I successfully deployed
and ran the application on Tomcat 6.x and 7.x.
I am unable to put the load on the application that the Reporter mentions;
however I am able to at exercise the tags mentioned and report that I am able
to display the associated text -- and not any keys -- in every instance.
I recommend this issue be closed unless additional information is introduced to
support that the bug exists.
> i18n tags lost value problem
> ----------------------------
>
> Key: WW-3057
> URL: https://issues.apache.org/jira/browse/WW-3057
> Project: Struts 2
> Issue Type: Bug
> Components: Other
> Affects Versions: 2.0.9
> Environment: JVM=1.5.0_16
> Struts 2.0.9
> Reporter: Pedro Miguel
> Fix For: Future
>
>
> i18n tags works OK. However, when many people access in the application, it
> doesn't get the values, and print the keys.
> For example:
> // ***** .properties file *********
> index.submit=Submit
> // ***** JSP file ********
> <s:text name="index.submit"/> //Print: "Submit"
> //THEN
> <s:text name="index.submit"/> //Print: "index.submit"
--
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
