problems with messages.properties

[gonorrhea]

I have some key/value pairs set in the messages_en.properties file as follows:

com.cox.ers.home.richPanel1.header=Outstanding Equipment by Next Actionable Step
com.cox.ers.home.richPanel2.header=Outstanding Equipment by Type
com.cox.ers.recoveredEquipmentManagement.richPanel1.header=Recovered Equipment Management
com.cox.ers.home.richPanel3.header=Recovered Equipment Management
com.cox.ers.appname=Equipment Recovery System

here is the xhtml:

<rich:panel width="500px">
                <f:facet name="header">
                    <h:outputText value="#{messages['com.cox.ers.home.richPanel3.header']}" />
               </f:facet>
               <h:outputText value="#{messages['com.cox.ers.home.richPanel1.header']}" />
               <h:outputText value="#{messages['com.cox.ers.recoveredEquipmentManagement.richPanel1.header']}" />
</rich:panel>

After JSF renders, the header value displays as follows: com.cox.ers.home.richPanel3.header

The 1st outputText displays as follows: Outstanding Equipment by Next Actionable

The 2nd outputText displays as follows: com.cox.ers.recoveredEquipmentManagement.richPanel1.header

Why are the keys and not the values from the properties file being rendered in some cases?  Very strange...

[luxspes]

This has happened to me when I do not do a cold start (completely stop the application server, and the restart it)

[gonorrhea]

Well I did just that (restart app server) and it is reading properly from the messagesen.properties file.

So is that a bug or is messagesxy.properties files not hot deployable?  The updated contents were visible in the props file in exploded EAR in server/default/deploy.

I was using ant explode the whole time so maybe if I did a ant restart instead it would have worked?