Hi Chris, I think the most flexible and reusable approach would be an XML-RPC servlet on the magnolia end (possibly built as a module). This would do all the content creation, and as it's embedded into the magnolia webapp it would be able to setup login sessions etc.
You could then just call this servlet from your external application, passing the user credentials, the content you want to create, etc. All you would need in your external app would be a URL to the magnolia instance and some login credentials. I know there was some discussion on the dev list about providing a standard feature to access the API via XML-RPC (see JIRA), but I don't know what the status is of this. There may be some base code in SVN that you could use, or you might be the one starting the actual coding on this! If it's something you would consider contributing back to magnolia then I (and others probably) would be happy to help with the development as I think it would be a really useful function. Simon On 12/03/07, Allan, CJ (Chris) <[email protected]> wrote:
Hi guys, We have a system which we would like to be able to add content to our magnolia website. I understand how to programmatically add content within the context of the magnolia webapp, but how do we get our separate system/application to do this - how do we specify where to find our magnolia instance? Cheers, Chris ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
