Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
Description
Hippo Connect uses the properties plug-in. When the site starts up, I get the message
"PropertiesManagerImpl is deprecated. Do not use because it has bad performance. Use CachingPropertiesManagerImpl instead. Possibly you need to adjust this in your spring beans."
I'm happy that I'm told what I should do. But then I find that I do instantiate the CachingPropertiesManagerImpl in my Spring config, and the instatiation causes the default constructor of its parent class - yes, the PropertiesManagerImpl - to be invoked, which prints above warning.
This should be improved by putting the warning into the following if-clause:
if (getClass().equals(PropertiesManagerImpl.class))
{ log.warn(...); }