Hi all,

The scenario is you have a large set of application configuration
settings comming from: ldap, property files etc.

The problem is many sections of your application depend on many
different configuration settings. I am bored of seeing a big fat and
evil global class having the indecent exposure smell that is used from
every point of the application and the "reading configuration
parameters" concern scattered all over.

Any ideas or approaches to address this very problem?

Given that configuration management is more close to a "non-funtional
concern" would it make sense using AspectJ and take the concern out of
the first OO dimension? examples? also would it bring in this case
another problem that configuration management needs another
"non-funtional concern" logging ...

Thanks in advance,
Best Regards,
Giovanni