struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "victorsosa (JIRA)" <>
Subject [jira] [Commented] (WW-4358) Bad properties file not detected
Date Thu, 31 Dec 2015 20:15:39 GMT


victorsosa commented on WW-4358:

I check this out on this class /struts/core/src/main/java/com/opensymphony/xwork2/util/

Everything seems to be like Juan said.

LOG.error("Could not reload resource bundles", e);

The message should appears in the logs for any missing message file or even message key.

Can you please double check this? My best guess is that you need to setup you log4j2 with
the correct classpath: com.opensymphony.xwork2; because everything seems to be OK.

> Bad properties file not detected
> --------------------------------
>                 Key: WW-4358
>                 URL:
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Other, Value Stack
>    Affects Versions: 2.3.14,
>         Environment: Tomcat7, Ubuntu Server 14.04 LTS
>            Reporter: Juan-Francisco Diez
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 2.5
> I had a problem in a properties file but the framework never warned me.
> The properties file was the default configured in struts.xml for i18n but the strings
never appear and the log said that there were no key defined.
> The problem was just a mismatch between a slash and a backslash in the properties file
but I spent lot of time to track the problem (about 8 hours probing lot of stuffs).
> I just see that the properties file was not in the ValueStack. Perhaps if struts can't
push the content of the properties file in the ValueStack, it  can put an advise in the log
of the container.
> I think that a framework like Struts must help developpers to find quicker the problems
and in this case it's not helping.

This message was sent by Atlassian JIRA

View raw message