Rob van Maris <[EMAIL PROTECTED]> wrote: > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Meeuwissen > > > > If I understand it well you want two classes: > > ReloadableModule extends Module > > and something like: > > AutomaticlyReloadableModule extends ReloadableModule > > Yes, if we can come up with a better name for the second: > ReconfigurableModule?
Hmm yes, but the first one is reconfigurable too, if you call reloadConfiguration.. I think the essence of using the FileWatcher is that it happens fully automaticly after changing the Module XML, so perhaps: WatchedReloadableModule? > Let's also be more specific about in what package these should go. > IMO these are utility, not core. Well, yes, but it is very related to module, so org.mmbase.module is a good spot I think (where i have put it now). Btw, I think org.mmbase.module should drasticly be cleaned. Most things currently there are either deprecated, or not even utils but applications. I would imagine in org.mmbase.module just Module.java and a few useful extensions like this ReloadableModule. The actual problem is that core is in module (org.mmbase.module.core) and not that module is in core. IMHO 'core' should obviously be implemented in org.mmbase.core, becasue even if MMBase.java is implemented as a Module, that is hardly its most important characteristic... Michiel -- Michiel Meeuwissen | Mediapark C101 Hilversum | +31 (0)35 6772979 | I hate computers nl_NL eo_XX en_US | mihxil' | [] () |
