Hi Dieter, I've just posted some code in response to a similar request which may help. My recommendation would be to use the Magnolia APIs for all content creation and manipulation, rather than messing with the underlying data layer. This way your code should be more insulated for changes to Magnolia, Jackrabbit, JCR, etc.
However, Magnolia doesn't currently have a very clean API for external integration, so it may be tricky to get everything working. I know there has been talk of a proper CMS API layer, and also a WebServices layer that would be even better for what you want to do. I don't know what the status is on either of these though. It would be good to hear from anyone that's involved in that work actually, as I have need of these features myself and would happily contribute to the development. Simon On 02/03/07, dieter <[email protected]> wrote:
Hi, I have been browsing through the tables on my Magnolia repository and have been wondering in which tables the actual data is stored. My reason for asking is i would like to eventually be able to automate creating new content externally from Magnolia. Is this possible? Dieter -- View this message in context: http://www.nabble.com/Viewing-MySql-tables-tf3334323.html#a9271918 Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
