thomason wrote: > > 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? > > Can you use Java DOM utilities to pull in the fragments you need from the > CMS? If you use an approach like that, then it would not matter which CMS > you used (though, of course, you will want to use Magnolia).
You mean something like building a DOM of the resulting page by putting together parts requested from a standalone CMS? We have lots and lots of existing JSP pages, and quite high performance requirements, so changing to an architecture that radical isn't possible. It's mostly plain JSP pages we have, but we're in a long-term transition to using Spring MVC as well. I don't have the luxury of letting the CMS solution dictate how our entire web solution will look, the CMS part is only a small part of the whole. That's why I'm looking for some way of integrating a CMS into... just about anything. :) /Anders ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
