Hi, I have the vague guts feeling, that this is not a good idea because it creates too big synchronized blocks.
Therefore I would think, that this is probably not a good idea to do. It would probably be better to enhance JavaDoc and tell "not thread-safe" in big fat red letters. (Of course this does not apply if I did not understand correctly, what this issue is about ;-) ) Regards Felix Jukka Zitting (JIRA) schrieb: > The abstract base classes in jcr-commons should be synchronized > --------------------------------------------------------------- > > Key: JCR-1793 > URL: https://issues.apache.org/jira/browse/JCR-1793 > Project: Jackrabbit > Issue Type: Improvement > Components: jackrabbit-jcr-commons > Reporter: Jukka Zitting > Priority: Minor > > > The abstract base classes like AbstractSession in o.a.j.commons implicitly > assume that a session and related objects (items, etc.) associated with that > session are never accessed concurrently from more than one thread. Instead of > relying on client code we should enforce thread-safety by explicitly > synchronizing potentially unsafe operations on the session instance. >
