Hi all, We've just released the first version of our site running on Magnolia, and we've got a list of things we'd like to improve. Some of the functionality we want would be best provided as modules: for example we intend to replace the current mail module with an implementation that can use Amazon's Simple Email Service instead.
My understanding of modules is that they are essentially the equivalent of .war or .ear archives. You create the desired functionality, bootstrap and so on, define the XML descriptor and then deploy your module into Magnolia. The module lifecycle is controlled by Magnolia and so on. My question relates to best practices for development and testing of modules. Those of you that have developed modules before, can you describe the process you take for development, test and deploy of modules? Other questions I have are: - What is the best way of testing Magnolia functionality in unit tests? I.e. lifecycle calls to modules? - What is the best way to tell Magnolia to "redeploy" a module? I look forward to hearing your experiences, cheers, Rob ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
