hi there.
I'd like to open a discussion on how to implement a module installer for
magnolia. I currently see two solutions and was wondering if there are
other solutions around people are thinking about.
solution a: installer/module manager is outside of magnolia
- we add an additional war file on to the server - that additional war
is responsible to manage the modules in the magnolia instances of the
server and can also redeploy the magnolia war files in order to apply
the changes
solution b: magnolia gets an internal module page where one can download
a module and run it. I'm wondering however in that scenario if magnolia
can be shut down enough and started again without having to restart the
app server.
Sidenote: it might be a good idea to move the module jar files into the
magnolia jcr repository instead of just dropping them into the
WEB-INF/lib path. Loading of a jar file can be achieved over a
dircontext extension the same way it was done for the better templating
module - however, this is app server dependent and different app servers
handle the dircontext differently. A guide on how to do this can be
taken from the spring framework runtime AOP weaving (they had to tackle
the same problem).
Would be great to hear other ideas/approaches and what your fav approach
would be.
Thanks
Ruben
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
