I have a site written in classic Spring MVC with jsp. I have the following requirements: 1- Create lots of content oriented landing pages that a non-developer people can easily edit. 2- Keep existing site as is, no major redesign or architecture changes. 3- Control how the URL of each page is generated.
It seems like Magnolia is definitely the right tool for #1. How about 2 & 3? Ideally, I would imagine requesting the content from Magnolia through a REST or Web Service call, the content would get retrieved and rendered in Magnolia and delivered to my app. I got this idea from this article: http://wiki.magnolia-cms.com/display/WIKI/Magnolia+and+Struts Am I getting this wrong? I already read this related thread: http://forum.magnolia-cms.com/forum/thread.html?threadId=c67f6b13-52d9-4304-a214-160ccec436bf&page=1 It seems to suggest that I need to create module in Magnolia to achieve what I want. I am still not understanding the overall architecture though. With this approach, do I keep my app running as a separate EAR/WAR in JBoss AND have Magnolia running along side with it? Or does my app run [b]embedded[/b] in Magnolia's war file? What's the purpose of creating a Spring module in Magnolia? What happens if I have requests that I don't want to involve Magnolia at all? like getting content from my app's database directly? Please help... -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=8e3d4c52-0bcb-47c6-80e4-914e46f686c5 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
