commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LOGGING-127) don't use setDefaultUseCaches() but setUseCaches() in LogFactory.getProperties()
Date Sat, 20 Sep 2008 16:41:46 GMT

     [ https://issues.apache.org/jira/browse/LOGGING-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Simon Kitching resolved LOGGING-127.
------------------------------------

       Resolution: Fixed
    Fix Version/s: Nightly Builds

Fix committed. Thanks for pointing that out!

By the way: what a wierd API - a non-static method that controls a static flag. 

> don't use setDefaultUseCaches() but setUseCaches() in LogFactory.getProperties() 
> ---------------------------------------------------------------------------------
>
>                 Key: LOGGING-127
>                 URL: https://issues.apache.org/jira/browse/LOGGING-127
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: Nightly Builds, 2.0
>            Reporter: Christopher Sahnwaldt
>             Fix For: Nightly Builds
>
>
> The fix for LOGGING-126 introduced a call to URLConnection.setDefaultUseCaches() in LogFactory.getProperties().
This call should be changed to URLConnection.setUseCaches(), because URLConnection.setDefaultUseCaches()
sets a static variable whose value affects the whole system, while URLConnection.setUseCaches()
only affects its target instance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message