<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/jconfig/patches/" rel="alternate"/><link href="https://sourceforge.net/p/jconfig/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/jconfig/patches/</id><updated>2007-03-16T13:37:47Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>shutdown of listener threads</title><link href="https://sourceforge.net/p/jconfig/patches/3/" rel="alternate"/><published>2007-03-16T13:37:47Z</published><updated>2007-03-16T13:37:47Z</updated><author><name>WolfgangWinter</name><uri>https://sourceforge.net/u/userid-1742278/</uri></author><id>https://sourceforge.net5d7d680f7b0035deebd86ae84b1ae38292749e14</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This patch may solve the problem reported by&lt;br /&gt;
Ernesto (ennova2005) - 2006-11-17 20:58   Memory Leak in 2.9.&lt;br /&gt;
I encountered some problems in a Tomcat application using jConfig which resembles the ones reported by Ernesto:&lt;br /&gt;
1. with the current run() method in FileWatcher, the watcher thread stops when the servlet thread finishes. That is not what I want.&lt;br /&gt;
2. On hot redeploy of the application the threads are not stopped and restarting them causes errors.&lt;/p&gt;
&lt;p&gt;To solve this I&lt;/p&gt;
&lt;p&gt;- added a shutdown() method to ConfigurationManager which must be called before exiting the application in order to stop all running threads. &lt;br /&gt;
In a j2ee environment it could e.g. be called in the destroy() method of a servlet.&lt;br /&gt;
- I introduced a flag for controlling in the run() method when the thread to stop.&lt;/p&gt;
&lt;p&gt;Changed sources:&lt;br /&gt;
ConfigurationManager&lt;br /&gt;
FileWatcher&lt;br /&gt;
FileListener&lt;br /&gt;
AbstractHandler&lt;/p&gt;
&lt;p&gt;check it and use it if you want.&lt;/p&gt;
&lt;p&gt;Apart from this:&lt;br /&gt;
One great missing disadvantage of current jConfig: The Property/Category watchers do not work when FileWatcher reloads a new Configuration because the Configuration object is exchanged and all registered Listeners are lost.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Bugfix 547153</title><link href="https://sourceforge.net/p/jconfig/patches/2/" rel="alternate"/><published>2002-05-03T07:05:39Z</published><updated>2002-05-03T07:05:39Z</updated><author><name>Andreas Mecky</name><uri>https://sourceforge.net/u/amecky/</uri></author><id>https://sourceforge.nete42970e1d7d4d7c2c18a7b8f173c559cd7677464</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is a jar file fixes the problem that every &lt;br /&gt;
getProperty writes some stuff to System.out&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>bug fixes</title><link href="https://sourceforge.net/p/jconfig/patches/1/" rel="alternate"/><published>2001-11-20T13:28:08Z</published><updated>2001-11-20T13:28:08Z</updated><author><name>Andreas Mecky</name><uri>https://sourceforge.net/u/amecky/</uri></author><id>https://sourceforge.netf554975dbc613f1cb0aaa5013adcd4af42c15727</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This patch includes:&lt;br /&gt;
- build.xml&lt;br /&gt;
- create.sh&lt;br /&gt;
- create.bat&lt;br /&gt;
to use Ant and the build.xml.&lt;br /&gt;
Please refer to the documentation to see how to use &lt;br /&gt;
it.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>