Why not have start and stop hooks for such stuff? Have an interface with onStart() and onStop() methods, and call them when you load and unload a class.
If you really need modularity, use OSGi. Regards, Erwin. > Sun Jun 19 2016 15:00:56 CEST from "Aplomb Chen" <[email protected]> >Subject: Groovy hot deploy in production > > > >Hi Guys, > > > >Will you use groovy hot deploy in production environment? Is it reliable to >do so? > > > >I am worried that it may have issue when you are doing below, > >1, Defined a Array as class attribute, make it has 10000 objects, next time >code hot deploy that the array is erased in code, then that must be an memory >leak, right? > >2, If you execute a periodic timertask in a groovy, next time code hot >deployed, if the timetask is no longer needed from your code, but the started >timertask will still be running, right? > > > >If we demands developers avoid using class attributes or starting any thread >thing as a development rule, will hot deploy still be good for production? > > > >Aplomb > > > >Best regards > > > > > > -- Erwin Müller - [email protected] Software Entwickler - (+49) 01577-9505569 Pgp - https://pgp.mit.edu/pks/lookup?op=get&search=0x02E820911DD910FD Meine Seite - http://www.mueller-public.de/ ANRI - http://www.anr-institute.com/
