[ http://issues.apache.org/jira/browse/CONFIGURATION-229?page=all ]

Oliver Heger resolved CONFIGURATION-229.
----------------------------------------

    Fix Version/s: Nightly Builds
       Resolution: Fixed

A fix was committed that causes the load() method to be invoked after 
initialization of all specified properties is completed. This should solve this 
problem. Please double-check.

Thanks!

> config : load for a configuration node is called before parsing is complete : 
> attributes ignored
> ------------------------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-229
>                 URL: http://issues.apache.org/jira/browse/CONFIGURATION-229
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.3 Final
>            Reporter: Andre Doherty
>         Assigned To: Oliver Heger
>            Priority: Minor
>             Fix For: Nightly Builds
>
>
> Hi there
> i have noticed the following issue which appears to be a bug. (Tested on 1.3 
> however the version doesn't appear above)
> createObject from FileConfigurationFactory(DigesterConfigurationFactory) set 
> fileName and fires load of properties : 
> public Object createObject(Attributes attributes) throws Exception
>         {
>             FileConfiguration conf = createConfiguration(attributes);
>             conf.setBasePath(getBasePath());
>             conf.setFileName(attributes.getValue(ATTR_FILENAME));
>             try
>             {
>                 log.info("Trying to load configuration " + 
> conf.getFileName());
>                 conf.load();
>             }
> However digester invokes createObject when the object is instancied and 
> before setting any attributes. 
> All other attributes beside fileName and basePath are not read in time and 
> therefore are ignored during load.
> I guess load should be called when node initialization is complete, possibly 
> using a proper digester rule. 
> Regards,
> andré

-- 
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]

Reply via email to