However, maybe this is something we should think of a bit better before we close down the vote and THEN have to start thinking of how to implement it.
I'm not talking packages here. I'm pretty sure it should go in org.mmbase.module.
A fe wthjoughts:
- don't see why we shoudl not make every module 'reloadable', that is: implement the reload() method and have it act properly (if needed). If every module has reload behavior, than it becomes easier to implement in the long run: all you have to do to reload a module is call the reload() method. How that is called is another matter.
- The filewatcher is a good way. it could be something more generic though, not related to a class implementation. Maybe it should also be a stanbdard faeture - perhaps like ModuelProbe, the Module class should have a thread that monitors all moduels and relaods them when the file changes. I don't see why a moduels houdl NOT be reloaded... Still if that is needed, we can always introduce a attribute in the module file's mdouel tag (reloadable="true"), to indicate whether a module file should be watched.
Iow, I am +1 for reloadable modules, but, on hindsight, -1 on modules whose 'reloadability' is determined based on extension of a certain class.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
