On 2/11/10 2:41 PM, Aaron Kimball wrote:
There are an enormous number of examples of the following line in user-side
code:
Configuration conf = new Configuration();
... This is going to need to still work transparently after any refactoring.
The new Configuration in this case needs to be popula
There are an enormous number of examples of the following line in user-side
code:
Configuration conf = new Configuration();
... This is going to need to still work transparently after any refactoring.
The new Configuration in this case needs to be populated with values from
the appropriate defaul
Eric Sammer wrote:
All (notably commiters):
In walking through the source, it seems that there are a number of cases
where static state exists. o.a.h.conf.Configuration is a good example of
a case were there is a static cache (see Configuration.REGISTRY) as well
as some class level state for def
All (notably commiters):
In walking through the source, it seems that there are a number of cases
where static state exists. o.a.h.conf.Configuration is a good example of
a case were there is a static cache (see Configuration.REGISTRY) as well
as some class level state for default resources. These
