jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric Esnault <f...@legisway.com>
Subject RE: How fragile is XMLPersistenceManager?
Date Wed, 06 Jun 2007 14:36:46 GMT
As far as i know :

1. XMLPersistenceManager should NOT be used for production, unless you do not need performance
at all;
2. JVM death is one of the "ugly" cases of your tests cases, and I would bet that XMLPersistenceManager
is not ready to assume this case. Take care to wrap your operations in transactions...and
forget the word "performance";
3.Repository consistency is essential imo, so as long as there is a possibility that yours
become inconsistent, then either fix this or change your options;
4. Yes, I think simpleDBPersistenceManager is - currently - the only safe one;
5. migration shouldn't be hard, connect to one persistence manager, use the session.exportSystemView
(or document view), then connect to the other one and import the data with session or workspace
imports (workspace import doesn't need a save, no session is used, changed are immediately
persisted).

BTW, I would be delighted to hear about your experience with Jackrabbit as a production CMS,
and I don't think I'm the only one. Please share your successes and problems with the community
;)

Frédéric Esnault - Ingénieur R&D
Legisway
60 boulevard de la mission Marchand
92400 Courbevoie La Défense
 

-----Message d'origine-----
De : Phillip Rhodes [mailto:spamsucks@rhoderunner.com] 
Envoyé : mercredi 6 juin 2007 16:32
À : users
Objet : How fragile is XMLPersistenceManager?


Long story short, I need to rush some applications to production because of circumstances
beyond my control...  Like today!

I have been running my jackrabbit repo in the test environment with the XMLPersistenceManager


How fragile is this persistance manager? I wouldn't worry if a certain node would be corrupted
if the JVM is killed in the middle of writing an XML file, but is it possible for the entire
repository to be corrupted?  That of course would be very, very bad...

Is the SimpleDbPersistenceManager the only safe bet?

How hard is to to migrate from one persistence manager to another?  Is it a custom migration
that I would have to write to manually read one repo and write to the other?

Thanks for all your help!

BTW, stitches on jackrabbit is going to be powering all the data-driven (not design elements)
images for one of the top tourism sites in the country :)




Mime
View raw message