Dear Henrik, according to "how" ... the answer is: you could use the benefits of Magnolia templates for your website (contents, graphics, and so on) and write an appropriate paragraph in Magnolia which pass needed parameters to a Spring (or other framework you like) servlet. Magnolia render the only paragraph, content in the paragraph is managed by Spring.
In my previous email I suggest Spring because seems Magnolia core will be "Springed" with version 3.5 (see http://jira.magnolia.info/browse/MAGNOLIA-608). finally, from SpringModules docs 10.5.2. "Magnolia": "Magnolia itself is not a repository and replies on a JCR implementation(Jackrabbit in particular) for its backend. Thus, connecting through JSR-170 to Magnolia is identical to connecting to a Jackrabbit repository." So you're not reinventing the wheel. Someone uses the same technique :D and integrated two products. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
