[
https://issues.apache.org/jira/browse/CONFIGURATION-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502701#comment-13502701
]
Lorenz Schumann commented on CONFIGURATION-511:
-----------------------------------------------
Although the project in which i noticed that behavior and where i wanted to
improve something got cancelled in the meantime, an improvement for resource
locating would be a nice thing to have :)
Thanks in advance!
> ConfigurationUtils cannot locate classpath file when current Thread is RMI
> --------------------------------------------------------------------------
>
> Key: CONFIGURATION-511
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-511
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.6, 1.8, 1.9
> Reporter: Lorenz Schumann
>
> I noticed the problem when a registered MBean method is invoked over JMX
> (=RMI) and it calls ConfigurationUtils.locate("some.properties").
> The classloader is not able to find the resource then.
> A possible fix would be to change
> ClassLoader loader = Thread.currentThread().getContextClassLoader();
> to
> ClassLoader loader = ConfigurationUtils.class.getClassLoader();
> in method locateFromClasspath. But i am not sure what other Effects that
> would have since I have no insight into commons-configuration.
> Tested with 1.6, 1.8, 1.9.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
