Philipp,
is it possible to get a sample xml configuration file for a module,
since need to migrate the one for openwfe.
Niko,
On Mar 15, 2006, at 3:28 PM, Philipp Bracher (JIRA) wrote:
[ http://jira.magnolia.info/browse/MAGNOLIA-761?
page=comments#action_11775 ]
Philipp Bracher commented on MAGNOLIA-761:
------------------------------------------
I commited the main code:
Lifecycle:
- ModuleRegistration (checks dependencies)
- ModuleLoader (initialization order follows dependencies)
Module Descriptor (betwixt used to read the modules xml descriptor):
- ModuleDefinition
- ServletDefinition
- RepositoryDefinition
ObservedManager (reloading after a registered node changed)
- ObservedManager
- ParagraphManager
- TemplateManager
- DialogHandlerManager
- ControlsManager
- TreeHandlerManager
- PageHandlerManager
Default Modoule Implementation: AbstractModule
- bootsraps the fiels config.modules.name.* in the resource folder
mgnl-bootsrap (additional files can be defined in the descriptor)
- copy files to the filesysten from mgnl-content/templates/module
and docroot/module (additional files can be defined in the descriptor)
- registers servlets defined in the descriptor
- registers repositories
- set restartNeeded flag if a servlet or repository was registered
- during the initialization all dialogs, paragraphs, templates,
controls, trees and pages are registered by there manager
I will add subtasks to define the open points.
Modules
-------
Key: MAGNOLIA-761
URL: http://jira.magnolia.info/browse/MAGNOLIA-761
Project: magnolia
Type: Sub-task
Components: core, admininterface
Reporter: Philipp Bracher
Assignee: Philipp Bracher
Fix For: 3.0 RC1
We have done the major step for modularizing magnolia. I would
like go a step further before we release 3.0.
Goal
----
- tie everything together (one jar per module)
- slim webapp (only stuff which an enduser concerns about:
templates, css)
- easier development process
Changes
-------
A) Additional Bootstrap
- A module has a bootstrap dir in the resources (during
installation the content get's imported)
B) Templates , .. per module
- Each module configuration has a dialog, paragraph, templates
config (instead of registering them in the templating module)
- The current templating module is renamed to samples
C) remove admindocroot and admintemplates
- only the template and paragraph jsps and resources are extracted
from the jar and written to the filesystem
- the resources used in the admin interface are served by the
resource servlet
- NO jsps for the admin-interface (see below)
D) New module definition no longer in the manifest file
- the definition is in an xml file META-INF/magnolia/xxx.xml
--> during development one has not always a proper jar (with
manifest)
E) subdir per module
- docroot/module
- templates/module
- if a new version is installed the dirs get rewritten completely
NO JSP in the admin interfaces
______________________________
In future we will use JSF and FreeMarker. As a mid-step I would
like to change the dialogpages (not the dialogs). We call them
newly pages. The default page uses a template named like the
classname. With this we can avoid the jsps in admintemplates. The
module register it's pages (like we do currently for trees, ...)
and a main servlet processes this pages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
