On Oct 13, 2010, at 14:24, CAPITAINE Harold wrote:
> Hi Gregory, > > > You're right I worked on a custom mysql persistence manager a long time > ago... > But my real interest, I would like not to use JCR because I personally think > that's too much instable with lots of contents. Moreover I had feedbacks > from people who worked with JCR also, and they had same problems. Are you talking about JCR (the spec) or JackRabbit? (ref. implementation of said spec, which we bundle with Magnolia) If the former, I'd like to hear more.. but I suspect you mean JackRabbit - and this has improved a lot in the latest versions; 1.6 was already a big improvement, and it seems 2.x is even better, like Richard suggests. > I didn't have a look on the core modules since 3.5, but I think they didn't > change so much. > Would it be possible to change the persistence layout by a custom one. Do > you think the code is enough flexible to do so? There are probably too many points for it to be reasonable to do it at Magnolia-level rather than at JCR-(the spec)-level. Richard makes some fair points; there are some efforts going on at the moment - we're hearing about Gigaspace-Jackrabbit integration, for example, which might be interesting for you. Cheers, -g ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
