To me, this sounds great in theory, but unlikely in practice: the point of configuration is that you can affect application behaviour without requiring regular redeployments. What you suggest seems only to be workable as a proper replacement for configuration if you use something like OSGi, which is its own can of worms.
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
As with most code smells, they are not rigid rules. I point for possible abuses, but I agree there are many valid scenarios.
I think you should carefully choose your own scenarios and decide if they deserve a configuration object (not a setting) . This will not require a new deployment. I will clarify the article
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To me, this sounds great in theory, but unlikely in practice: the point of configuration is that you can affect application behaviour without requiring regular redeployments. What you suggest seems only to be workable as a proper replacement for configuration if you use something like OSGi, which is its own can of worms.
Hi Alain!
As with most code smells, they are not rigid rules. I point for possible abuses, but I agree there are many valid scenarios.
I think you should carefully choose your own scenarios and decide if they deserve a configuration object (not a setting) . This will not require a new deployment. I will clarify the article