Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an application structured as follows:
I’ve made a class that reads the application configuration from an XML file. The question is where should it be placed?
By reflex, I’d have placed it in utilities but utility classes have static methods and are stateless whereas this class uses an instance of Apache Commons XMLConfiguration. Should I just adapt the methods so this instance is limited to the scopes of the methods in this class?
I assume the items are packages, so I’d go with the main package.
Why? The configuration of an application, whether it be in XML or not and whether it is based on an application framework such as Spring or not, is part of its main functionality. Booting up an application is the main responsibility of the application. All the business functionality, all the shiny features it provides are implemented in the domain and service layers.
You’re right, utils is all about static or similar tools. As the configuration of an application is very important, I wouldn’t declare it a utility. A utility is something which can be easily replaced by another utility of same type (e.g.
StringUtilvs.StringUtilsvs.IOUtilsetc. they all have very similar functionality)