[ http://issues.apache.org/jira/browse/CONFIGURATION-216?page=all ]
Joerg Schaible reopened CONFIGURATION-216:
------------------------------------------
Reopened by request. Since the bug is "only" resolved, you should have been
able to do so yourself. But maybe there's a flaw in the JIRA workflow
configuration ...
> Inconsistent way to locate filename when creating configuration
> ---------------------------------------------------------------
>
> Key: CONFIGURATION-216
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-216
> Project: Commons Configuration
> Issue Type: Bug
> Environment: commons-configuration-1.3-dev
> Reporter: Gabriele Garuglieri
> Assigned To: Oliver Heger
> Priority: Minor
> Attachments: 216.patch
>
>
> There is a different behaviour locating the configuration file in classpath
> depending on the way it is set in the configuration class.
> For example assuming "conf/conf1.properties" exists in classpath:
> PropertiesConfiguration pc = new
> PropertiesConfiguration("conf/conf1.properties");
> gives org.apache.commons.configuration.ConfigurationException: Cannot locate
> configuration source conf1.properties
> while
> PropertiesConfiguration pc = new PropertiesConfiguration();
> pc.setFileName("conf/conf1.properties");
> pc.load();
> properly locate file in classpath and loads it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
