From:
<S.S...@au...> - 2003-01-22 19:03:54
|
Hello Pascal, > I've got a liitle class, used in some other java apps, that handles, > pretty nicely, a global properties file containing the config variables. > If you want to go the properties way for externalizing config variables, I > suggest taking a look at my class (see attachement, package has to be > adapted of course <image.tiff>). > > I am always hesitating between a regular Java properties file and an XML file Maybe you have arguments that can help to choose between the two. Anyway, your class (and my hesitation) only address part of the problem : the reading and writing of the data itself. This is only the top of the iceberg on this topic and the most easy part to solve :-) The real problem, according to me, is to let the client figure out where the configuration file is and how he can read/write to it. As you have noticed, a JWS application can not write the file system as easily : we have to use JWS storage services. On the other hand, since we are in the context of a web application : i really like the idea of having the user's properties stored on the server (and the file being exchanged through opensst messages). This solution solves all deployment issues we are facing > P.S.: Bytheway, I test the stuff about the server being behind a proxy, > works ok and is really easy to implement. The use a config properties file > for tis too would be perfect. > > I really would like to see your modif (even with hardcoded proxy) The output of a "diff -c"is fine for me. I can commit that in the CVS tree Thanks for the effort and your suggestions Seb |