On 23.05.2007, at 00:20, thomason wrote:
on 5/22/07 8:46 AM, Theodore Nguyen-Cao at [email protected]
wrote:
Hey,
Has anyone had experience with pulling Magnolia content into a
different
application context?
Since Magnolia lives in its own application context, what I would
like
to do is pull in Magnolia content (HTML, CSS, images, js, flash,
etc.)
into a separate application context to serve up in snippets.
We pull the snippets off into Cocoon pipelines. That way, pages are
constructed on-the-fly from a mixture of CMS-managed content
(Magnolia),
database information, backend applications, etc. Integration is
easy because
it is all xml.
And maintenance is a nightmare b/c its all in XML ;-)
Cheers
Boris
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
