thomason wrote: > We have taken a similar approach using Magnolia to provide a back-end CMS > that feeds XMLized fragments (from the Public interface) to an exposed > Cocoon front-end. (<http://www.utmem.edu/Facsenate>). This approach enforces > a separation of content from presentation, provides a security layer, and > Cocoon provided the right fit for some of the data we serve.
While we'll probably be XSLT-transforming some stuff, we'll be mostly just outputting lumps of HTML directly in existing pages, mostly plain JSP. > > But we'll need to run this stuff inside of > > our existing web-app, so deploying a separate War file is out of the > > question. > > Just my opinion, but I am leaning away from such tight integration because > it is harder to maintain when updates and bug-fixes arrive frequently. Yeah, it would be nice to have it completely separated. But I don't see how we could serve parts of pages in our legacy application with the CMS running outside of it? /Anders ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
