1. Don't need to code retry logic. If getInstance() throws exception, INSTANCE will still be null so next call will just try again.
2/3. This will depend on the situation. In most cases, I think we can simply remove the static variable and put a method call to Confg.getInstance().getProperty into the method. In the case of other static blocks like ApacheDsDataProvider, they will probably have to be modified to have the same new singleton pattern as Config. There is a ripple effect through the code if we take this approach, so wanted to get everyone's buy in before I make all the changes. Side Note: may want to change ApacheDsDataProvider class name since it's not specific to ApacheDS, correct? ----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Wednesday, March 16, 2016 10:49:51 AM Subject: Re: Static Config Initialization Problems > On Mar 16, 2016, at 9:44 AM, Shawn McKinney <[email protected]> wrote: > > 2. The config object is used throughout the code, in static blocks, static > variable initializations and such. Left question off #2, but is basically same as #3. How would you recode the classes using the config instance in static variables or blocks?
