The 4.3 release notes at http://documentation.magnolia-cms.com/releases/4-3.html state:
> Paragraphs can be rendered independently via the URL; opens > door for integration with other systems by allowing to get and > render content snippets. (Ajax, REST, ...) A comment at that page also claims: > with Magnolia 4.3 is allowed requests to paragraphs (snipped/ajax) > in terms that URI to a paragraph renders the paragraph (without any > page rendering) by extending the AggregatorFilter That makes me wonder about best practices for server-side Ajax controllers (for magnoliaPublic). 1- I've seen JSPs being put in the document root, to be invoked by Ajax calls (just like at http://wiki.magnolia-cms.com/display/WIKI/Add+Magnolia+MainBar+functionalities+with+Ajax ). 2- In 4.2.3, one can create pure Java controllers using Blossom, but as far as I know this still requires one to include a Blossom-managed Paragraph in some dummy page, to get a URL one can actually invoke (a bit like described at http://www.mail-archive.com/[email protected]/msg00165.html ). 3- I've seen info.magnolia.module.admininterface.PageMVCHandler being (a)bused (in combination with relaxing the Anonymous Role to allow web site visitors requesting some "/.magnolia/pages/myAjaxResponder" URL). 4- I've tried to use plain Spring MVC, but even when adding bypasses (to Configuration, server, filters, cms), my controller just doesn't get invoked (though I can see Spring registering the URL I specified using @Controller and @RequestMapping). Any ideas on the best or better ways to do this? Thanks again, Arjan. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
