[SLING-786] SessionPool logs out session on release when locking or observation is not supported

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JCR Base 2.0.2
• Fix Version/s: JCR Base 2.0.4
• Component/s: JCR
• Assignee: Felix Meschberger
• Reporter: Marcel Reutegger
• Created: 18/Dec/08 13:04
• Updated: 18/Dec/08 22:35
• Resolved: 18/Dec/08 15:36

Description

There should be a check whether the repository actually supports locking before a query is executed to get the lock tokens. Similarly the SessionPool should first check if observation is supported by the repository before the ObservationManager is obtained. In both cases it may happen that a repository that does not support one or the other feature throws a RepositoryException, which causes the session to be closed. This effectively makes the SessionPool useless in that case.