Add support for natively supplied FeatureLocking

Description

ContentFeatureStore assumes that every subclass of ContentDataStore uses the InProcessLockingManager as it's locking manager. This prevents subclasses from supplying their own FeatureLocking implementation. In the attached patch, this assumption has been relaxed using the same design pattern that allows ContentDataStore subclasses to supply their own filter, retype and reprojection capabilities.

Environment

None

Assignee

Unassigned

Reporter

codehaus

Triage

None

Components

Fix versions

Priority

Medium
Configure