What is the best approach for Messagesource?

[Roberto Tucci]

Hi,
I'm building a new web app using Spring MVC 4 (under Tomcat) and I need to know what is the best approach to store the message source in my webapp.
Actually, I'm thinking to use the Spring properties file to manage all labels but I have some questions to ask: if I add a new message in my properties file, do I need to redeploy my webapp on Tomcat (stop server -> deploy -> run server)?
The second question is this: could be the database driven resource the best approach for this? In this case, i could avoid to redeploy the webapp on Tomcat (because my message resources are managed in my database)...

Thank you!!

[K. Tsang]

Roberto Tucci wrote:Actually, I'm thinking to use the Spring properties file to manage all labels but I have some questions to ask: if I add a new message in my properties file, do I need to redeploy my webapp on Tomcat (stop server -> deploy -> run server)?

You should use Spring resource bundle configuration to read your messages.

If your properties file is inside your WAR, updating it will need redeploying.

Roberto Tucci wrote:
The second question is this: could be the database driven resource the best approach for this? In this case, i could avoid to redeploy the webapp on Tomcat (because my message resources are managed in my database)...

True putting such labels in DB will avoid redeploying. However, think about how you will access these messages since fetching every time is not a good idea.

[Roberto Tucci]

K. Tsang wrote:

Roberto Tucci wrote:Actually, I'm thinking to use the Spring properties file to manage all labels but I have some questions to ask: if I add a new message in my properties file, do I need to redeploy my webapp on Tomcat (stop server -> deploy -> run server)?

You should use Spring resource bundle configuration to read your messages.

If your properties file is inside your WAR, updating it will need redeploying.

Roberto Tucci wrote:
The second question is this: could be the database driven resource the best approach for this? In this case, i could avoid to redeploy the webapp on Tomcat (because my message resources are managed in my database)...

True putting such labels in DB will avoid redeploying. However, think about how you will access these messages since fetching every time is not a good idea.

Thanks!

I'm thinking to store a static object with all labels from DB (loaded on first deploy and available always without access on db every time)...could be a good idea? the application should be deployed anyway when i change a label on db...it's right?