You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Emmanuel Bourg (JIRA)" <ji...@apache.org> on 2007/04/26 00:48:18 UTC
[jira] Updated: (CONFIGURATION-63) [configuration]
ConfigurationUtils.locate throws NullPointerException if the context
ClassLoader is null
[ https://issues.apache.org/jira/browse/CONFIGURATION-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Bourg updated CONFIGURATION-63:
----------------------------------------
Affects Version/s: (was: 1.2)
1.3
> [configuration] ConfigurationUtils.locate throws NullPointerException if the context ClassLoader is null
> --------------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-63
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-63
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Operating System: Windows XP
> Platform: PC
> Reporter: nomus
>
> Hello,
> When the locate method attempts to find resource location from the context classpath
> (lines 375-384 in ConfigurationUtils.java) it fails (on line 378) if the context
> ClassLoader cannot be retrieved for the current thread.
> I suppose this bug is quite difficult to reproduce. I came accross it when I and a
> colleague of mine were testing a Java API (kept in one jar) that is called from C++
> application. In the static initializer of a Java class I used the next line to load
> settings:
> config = new PropertiesConfiguration(ConfigurationUtils.locate("properties/routing.
> properties"));
> It worked fine if the class was used from another Java class that was normally loaded
> by JVM (for example my tests passed). But when my Java classes were executed by JVM
> started from C++ application it resulted in the next exception:
> java.lang.NullPointerException
> at org.apache.commons.configuration.ConfigurationUtils.
> locate(ConfigurationUtils.java:378)
> at org.apache.commons.configuration.ConfigurationUtils.
> locate(ConfigurationUtils.java:255)
> ...
> It is obvious from the ConfigurationUtils code that loader variable got null value
> (line 377) for some reason so the next step threw the exception.
> I suppose this bug can be easily fixed (just to add an additional check if loader is
> not null).
> As a workaround I will try to call locate method with a given base parameter (but it
> needs to determine location of my jar so it is a kind of overheads though it would
> work I hope).
> Sorry for my English.
> Hope it is useful,
> Denis
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org