You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Dennis Lundberg (JIRA)" <ji...@apache.org> on 2009/12/29 18:14:29 UTC

[jira] Closed: (LOGGING-127) don't use setDefaultUseCaches() but setUseCaches() in LogFactory.getProperties()

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

Dennis Lundberg closed LOGGING-127.
-----------------------------------

    Assignee: Simon Kitching

> 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
>            Assignee: Simon Kitching
>             Fix For: 1.1.2
>
>
> 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.