The first thing that comes to mind is that all configurable paths, both in the database and property files, should be relative to a common "base path". This way I could deploy the application on different paths in different environments (development, test, etc.), and configure just one property if I don't have any particular need of, say, moving the "templates" folder for instance.
Another idea more on the post subject: having the context path in the url should be considered as "uncommon". What I mean is that nobody serious about his business would ever want a "konakart" context appearing in his shop urls, so the distribution should come out-of-the-box with that in mind. The shop application should be deployed in the "ROOT" folder of the tomcat webapp directory. This way, I won't have to move the app when deploying to production and I'd have less configuration tweaks to do.
Another idea more on the post subject: having the context path in the url should be considered as "uncommon". What I mean is that nobody serious about his business would ever want a "konakart" context appearing in his shop urls, so the distribution should come out-of-the-box with that in mind. The shop application should be deployed in the "ROOT" folder of the tomcat webapp directory. This way, I won't have to move the app when deploying to production and I'd have less configuration tweaks to do.