Be the first to like this
ntegrating custom software into Magnolia modules is a given nowadays. Only, all to often the frustration starts when you're using numerous modules and their Spring contexts and other configurations; this can be a real hassle. At Orange11 we do quite a bit of integrating Spring configured custom software into Magnolia modules. For example: when we need to load content from an external database into the Data module, or when we want to create a Blossom dialog that renders a select box based on results from an external web service.
We usually create a separate, reusable and testable modules. The services that need to be exposed are configured in a number of Spring contexts. When you are using a lot of these modules, the context management isn't ideal. Loading several contexts, editing the web.xml, for all modules. That's why we're introducing the Magnolia Spring Context Loading Module and we want to take this opportunity to tell you all about it. After this track you will be able to neatly integrate your Spring configured software, while taking full advantage of Magnolia's rich dynamic configuration.