Anders, > Our > old CMS currently serves various fragments of pages in JSP-based system > and the occasional whole page. What we need is something that can be > integrated into that relatively painlessly.
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. > 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. Donald B. Thomason, Ph.D. Professor, Department of Physiology College of Medicine University of Tennessee Health Science Center ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
