This class only exists to dissuade you from calling activate() directly on an
Activatable object.
Lock() -
Constructor for class org.crosswire.common.activate.Lock
You might be wanting to construct a Lock if you want to call
Activatable.activate() directly, in which case you stand a chance of
breaking the Activator, so let the activator call activate(), and just
ask the Activator to do the job for you.
If things want to prevent event firing because they are doing a set of
changes that should be notified in one go, they should call
raiseEventSuppression() and when done call this.
If things want to prevent normalization because they are doing a set of
changes that should be normalized in one go, they should call
raiseNormalizeProtection() and when done call this.