Open GoogleCodeExporter opened 9 years ago
Carefully being key as threads are outside of the j2ee spec and can cause memory
leaks in app servers. It would probably be worth making the usage of a thread
configurable and check the file when the configuration is accessed instead if
the
thread is disabled. A asynchronous bean or the like is another possibility but
that's
getting app server specific and requires external configuration...
Original comment by schal...@darkmist.net
on 16 Jan 2010 at 3:17
Original comment by manico.james@gmail.com
on 1 Nov 2010 at 12:52
This may or not not be necessary pending changes for 2.1 configuration
Original comment by chrisisbeef
on 20 Nov 2010 at 9:57
Original comment by manico.james@gmail.com
on 29 May 2012 at 3:23
Original issue reported on code.google.com by
manico.james@gmail.com
on 12 Jan 2010 at 4:17