Hi Paul,
Thanks for responding!
Here below is the whole story.
It is a
maven project involving technologies like Springboot and ORM framework.
The DB is oracle and we have a constants file from which constants are consumed, properties file which gets loaded to udeploy and the
Java files with usual
J2EE project structure.
The properties file is used to load the properties needed for starting the application.
We developers act as maintenance people also to maintain the application
With this scenario, I see that having 30-35 exception messages in database as a bad way to design a web application.
Because I feel business exception messages are supposed to be taken from the business layer and not from the DB layer.
Though the reason given is that we are forced to deploy every time we see a change or maintenance of the exception message(s)
My suggestion is to have these messages added as part of the constants file itself, and frequest deployment cannot be a reason for a poor design!
Ideas/suggestions please!
Thanks!