About module handling: I was thinking about adding a (maybe optional) "reload" lifecycle (a reload method automatically called when anything in the module configuration is changed). This will save modules to manually register jcr listeners like they do now. WDYT? Already implemented in your changes or is something I could work on?
I moved the responsibility for the listener registration to the managers. They inherit OberservedManager in common which handles this (registration, reloading, using uuids to re register,...)
But still it would be nice to inform the module (in general) if the modules config branch changed. Quite easy to do by changing the default AbstractModule class.
Perhaps we can discuss this after checking in (based on the code). I think there are still improvements possible ;-)
One of my problem is that the dialog handlers and the tree handlers are in the admin interface, where the paragraphs and templates are in the core module. What do you think about a core module (repositoriy, main servlets, ...) and a cms module (dialogs, paragraphs, default module implementaiton, ...).
The main problem is that a paragraph should know it's dialog. The other problem is not functional but it is not easy to find the responsible classes easily.
An other option would be putting this into the gui module, but since there is a refactoring planed I prefer otherwise.
Philipp Bracher ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
