|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Regarding Configuration files
Submitted by lsreedhar on Thu, 04/30/2009 - 05:47.
Hi All, I need to take a design level decission in using configuration files and request to provide your inputs on this.
My product is having a single configuration file covering the basic configurations. While using this for a project the no of lines in this configuration file is exceeding 4000 lines.
So my developers comming back and suggesting to have this configuration file to be splitted into mutiple.
But my concern here is that if we split the configuration files, it will be difficult in handling mutiple files and tracking on what configuration goes into which of configuration files will be very difficult
Also to my view its better to have a single configuration file as this file gets loaded only once into memory and that way increase performance when compared with using many configuration files.
Request to provide your thoughts on the same.
Thanks,
Sreedhar