Hello
Philipp Bracher (JIRA) wrote:
[ http://jira.magnolia.info/browse/MAGNOLIA-761?page=comments#action_11769 ]
Philipp Bracher commented on MAGNOLIA-761:
------------------------------------------
I have changed the following (not yet checked in):
Better initialization process:
- ModuleRegistration
- ModuleLoader
Module definition:
- a module has a xml descriptor (definition, dipendencies, servlets, repositories, ...)
Default module:
- can have and loads: dialogs, paragraphs, templates, trees, controls
--> the content of one module (for example the samples module) is tied together
now
Observation:
- the managers inherit ObservedManager which handles the observation
centralized (no
registration of listeners everywhere)
Configurable:
- ParagraphManager
- TemplateManager
- DialogManager
- ControlsManager
...
Resources:
- removed the admindocroot
- some util methods to handle resources (in jars and classes dir)
It might be a bit late, but the idea just came up to my mind.
Would it make sense to implement the modules infrastructure as analogous
as possible to the portlet specification (JSR 168) ?
Lifecycle, configuration management and the forth could be a source of
inspiration and maybe even code could be borrowed.
- Portlets also are hot deployable into portlet containers
- standards, standards, standards
I'm aware of the fact that modules need a bit more of configuration
informations than portlets. And in turn, modules might not need all
configuration information that portlets need. But maybe the intersection
is big enough? WDYT?
--
Cheers,
Michael
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
