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:06:29 UTC
[jira] Updated: (LOGGING-10) SimpleLog uses
getSystemResourceAsStream to load props
[ https://issues.apache.org/jira/browse/LOGGING-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated LOGGING-10:
-----------------------------------
Fix Version/s: 1.0.1
> SimpleLog uses getSystemResourceAsStream to load props
> ------------------------------------------------------
>
> Key: LOGGING-10
> URL: https://issues.apache.org/jira/browse/LOGGING-10
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Operating System: All
> Platform: All
> Reporter: John Rousseau
> Fix For: 1.0.1
>
>
> The Log implementation, SimpleLog, uses getSystemResourceAsStream() to load the
> simplelog.properties file. Using getSystemResourceAsStream(), instead of something like
> this.getClass().getClassLoader().getResourceAsStream(), or even better,
> Thread.currentThread().getContextClassLoader().getResourceAsStream(), prevents the
> properties file from being deployed with an application. This forces the developer to put the
> properties file on the system classpath.
> Why was the decision made to only look on at the
> system classloader? The LogFactory does a nice job of finding it's properties with
> findClassLoader(). A similar implementation for SimpleLog would be great.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.