Anders, >>> 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?
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). ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
