Hi Richard Thank you for your answer
[quote] ... What I am wondering more though is why make the move to JCR at all? If you have an existing web-app, with existing screens and a working database, why not integrate this into magnolia directly, rather than rewriting it to use JCR? [/quote] Well there are several aspects * We burn a lot time with problems of the persistence layer, mostly with hibernate problems. Blame this on our knowledge of hibernate ORM. * The problem domain doesn't require a strict schema, therefore I consider an alternative to a relational database. NoSQL comes to mind, but why not JCR? * JCR itself is a simple, (mostly) polished API. * Magnolia is a great product, we are using it successfully for several products * The frontend is written in Vaadin, Magnolia is using Vaadin, and thank to your and Ueli Scheidegger (and others, I am sure) work, the integration of a Vaadin GUI should be trivial I know there are risks, and they should not be taken lightly, but currently I do not see an killer argument against this migration... -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=45bf35a1-7363-4f5a-be99-0f44631811a4 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
