Object PM con: - non-transactional
meaning XA or is the Object PM not even atomic when using versionning/locking ?
If jackrabbit with an Object PM crashes while it is storing nodes, only parts of the nodes might get written. those nodes will still be visible when jackrabbit is started up again, even though the transaction has not been completed. I guess fixing this would make a nice patch or contribution ;)
using a database backed PM with such a scenario, the database would simply rollback the unfinished transaction.
regards marcel
