Joseph Shoop wrote: > Looking over the documentation and sample app for Blossom it looks great. > Perhaps this is not the right place, I am coming from a Spring background, > and not a Magnolia background, but is Blossom the best way to add Magnolia to > an existing Spring site? I have an existing Spring MVC app and would like to > add Magnolia capabilities to many of the pages. I am not really understanding > how the architecture works, do I need to have Magnolia running in my Spring > app, or just Blossom, and Magnolia running on another instance/machine? Is > Blossom the best way to do this, or just integrate into the filter chain? > Sorry, couldn't find any basic "Drop Magnolia into Spring" links....if you > have any suggestions, I would really appreciate it!
Blossom is a way to work with Spring Framework in Magnolia, not a way to work with Magnolia in an arbitrary application that uses Spring Framework. What do you expect from 'adding Magnolia to an existing Spring site'? Magnolia is a system to manage content on pages, I don't really see how one would be able to add Magnolia capabilities to pages in another system. Nils. ------------------------------------------------------------------------ VPRO www.vpro.nl ------------------------------------------------------------------------ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
