RE: Config constructor ignores ConfigFile contents

"Thorsten Hilker" <[email protected]>
Newsgroups gmane.comp.java.enhydra.general
Message-ID <000c01c30f0a$a97ae900$6500a8c0@kronos>
Once I had problems with the Config() - constuctor too.
Maybe that works:

...
com.lutris.util.Config conf = configFile.getConfig();
conf.set("first","a");
...

HTH

Thorsten

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Karl Stenerud
> Sent: Wednesday, April 30, 2003 5:29 AM
> To: [email protected]
> Subject: Enhydra: Config constructor ignores ConfigFile contents
> 
> 
> I'm trying to get a Config object from a file, but the 
> constructor for 
> Config() ignores the file's contents.
> 
> If I run the following code:
> 
>     java.io.File file = new java.io.File("multiserver.conf");
>     com.lutris.util.ConfigFile configFile = new 
> com.lutris.util.ConfigFile(file);
> 
>     java.io.File outFile = new java.io.File("/tmp/conftest");
>     java.io.FileOutputStream outStream = new 
> java.io.FileOutputStream(outFile);
>     configFile.write(outStream);
> 
>     com.lutris.util.KeywordValueTable blah = new 
> com.lutris.util.KeywordValueTable();
>     blah.set("first", "a");
> 
>     com.lutris.util.Config conf = new com.lutris.util.Config(blah, 
> configFile);
> 
>     org.apache.log4j.Logger.getRootLogger().error("Properties: " + 
> conf.toString());
> 
> 
> It prints out the following:
> 
>      [java] 626 [main] ERROR root  - Properties: {first=a}
> 
> 
> It is completely ignoring the data in multiserver.conf.  If I try the 
> constructor that takes only the config file, it also ignores the file 
> contents.
> I've verified that the ConfigFile is reading the file by 
> checking the output 
> file /tmp/conftest.
> 
> 
> _______________________________________________
> Enhydra mailing list
> [email protected] 
> http://www.enhydra.org/mailman/listinfo.cgi/en> hydra
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.