Hi guys, We have two existing webapps and we want to use Magnolia to manage some static/dynamic pages of both webapps. Let's say the two webapps are foo and bar where both are Spring powered webapps. More technical details are listed below:
- foo is mainly comprised of several standard Spring MVC controllers, which, by passing into different request parameters, generate thousands of pages that are search engine friendly. The urls of the pages appear to be static pages, even with html extension, but the pages are actually generated on the fly. We want to manage these dynamic pages with Magnolia, such as inserting content areas (paragraphs) that are managed by Magnolia into each of the pages. - bar is more complex than foo, but most of the pages we're interested in for CMS are pure jsp backed pages. However, we cannot say there won't be any dynamic pages as mentioned in foo that we want to manage with CMS. Until now we have implemented a CMS demo: - the demo uses Magnolia Blossom to integrate Magnolia into foo, which means Magnolia and foo are in one webapp in one container - for demonstration, we converted one Spring MVC controller into a @template controller (along with necessary paragraphs and dialogs) - by using virtualURIMapping and @template controller request parameters, we now can insert the same set of paragraphs into all the pages originally generated by the Spring MVC controller, which are actually backed by only one blossom @template controller *However, what we want to achieve in the near future are:* - Magnolia can manage static/dynamic pages of both foo and bar - We prefer Magnolia exists as a separate webapp instead of being currently deep integrated into existing webapps We currently don't have any solutions. But we do have some thoughts (or confusions) on that: - Because we have to manage dynamic pages, we cannot just let Magnolia alone to do that, instead we have to combine Magnolia's CMS functionality and the business logic of foo and/or bar (via Blossom) to achieve that. - Inspired by this chapter of the documentation ( http://documentation.magnolia-cms.com/technical-guide/instances.html), can we set up an architecture such that one author instance for authoring management, and two public instances among which one is integrated into foo and another into bar. However, this is obviously not a good solution, not to mention its feasibility. Could someone please be so kind to give some suggestions or clues on this? Thanks in advance. -- Best regards, Kenyth Zeng ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
