commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <>
Subject [jira] Updated: (CONFIGURATION-63) [configuration] ConfigurationUtils.locate throws NullPointerException if the context ClassLoader is null
Date Wed, 25 Apr 2007 22:48:18 GMT


Emmanuel Bourg updated CONFIGURATION-63:

    Affects Version/s:     (was: 1.2)

> [configuration] ConfigurationUtils.locate throws NullPointerException if the context
ClassLoader is null
> --------------------------------------------------------------------------------------------------------
>                 Key: CONFIGURATION-63
>                 URL:
>             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 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(
> 	at org.apache.commons.configuration.ConfigurationUtils.
> locate(
> ...
> 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:
For additional commands, e-mail:

View raw message