Hello Emmanuel,
Thanks very much for the clarification! Can you also shed some light on the performance issue when the reloading mechanism is used versus when not used?
Thanks again! Qingtian
Emmanuel Bourg wrote:
Hello Qingtian, a reloading strategy is passive, it doesn't spawn a thread to monitor the file, instead it checks if the file changed everytime a property is accessed. So just use it as a replacement for java.util.Properties.
Emmanuel Bourg
WANG Qingtian wrote:
Hi,
Is the reload strategy implemented by creating a thread that periodically checks the time stamp of the configuration file? If so, how do I make sure that thread is started/stopped properly when I use it in a j2ee container? Like, will the thread be killed when I shut down the web/ejb container? What is the "best practice" of using "configuration" in a j2ee container?
Thanks a lot for your help!!! Qingtian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
