jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "PersistenceManagerFAQ" by edgarpoce
Date Thu, 09 Jun 2005 12:51:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by edgarpoce:
http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ

------------------------------------------------------------------------------
  
  === How smart should be a PM? ===
  A PM should not be 'intelligent', it should not 'interpret' the data. The only thing it
should care about is to efficiently, consistently and reliably store and read the data encapsulated
in the passed nodeState & propertyState objects. Though it might be feasible to write
a custom persistence manager to represent existing legacy data in a level-1 (read-only) repository,
I don't think the same is possible for a level-2 repository and i certainly would not recommend
it.
- 
- === What about ORM-backed PMs? ===
- Persistence managers that store the item states in a complex schema are not the right way
to go. Keep it simple, e.g. the objectPersistenceManager stores the item states as a raw stream
of bytes.
  
  === What combination of FS and PM is the best choice? ===
  It depends on your priorities. If you want to store your data in an accessible format (just
in case ;), you might want to try XML PM + localFileSystem. If you use windows and performance
is a must, you might want to try objectPersistenceManager + cqfs.
@@ -41, +38 @@

  
  === ORM persistenceManagers ===
   * Status: work in progress
-  * Unnecessary complexity
+  * Not so simple
   * transactional
   * rdbms referencial integrity (possible, but not implemented yet)
   * not so easy to configure.

Mime
View raw message