hello Armin We have a similar use case: page comments. they are created on the public nodes, and must be moderated on the author instances. With magnolia you can configure your storage settings for each workspace. What we did is create a shared (formum) workspace for both the public instances and the author instance. that solved the problem for us: everything created on one of the nodes is immediately available on all the other nodes.
hope that helps, Ernst 2011/3/2 armin weisser <[email protected]> > Hi all, > > > > we have a standard magnolia scenario here with an author and a public > instance, each having its own data store. > > With this publishing new content from author to public is straight forward. > > > > We’re just facing the problem that the webapp itself alters content in the > public instance and we’d like to instantly propagate these changes to the > author instance (resp. its data store). > > > > So we need some sort of automatic reverse publishing process. > > > > The home grown, naive approach would be to observe changes in the public > instance and send a http request to the author instance. > > I also read about using JNDI to enable RMI calls … > > Another possible solution would be to handle this on the JCR level. > > > > Is there a „standard“ way of doing such things with the Magnolia-API? > > > > Cheers, > > > > Armin > > > ------------------------------ > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > -- Ernst Bunders Ontwikkelaar VPRO ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
