Previously I tried to describe the difference between dynamic and non-dynamic DFC preferences as the existence of some special code which is capable to modify DFC’s state in runtime, however there are some dumb cases which can’t be covered by this definition, for example com.documentum.fc.client.impl.session.StrongSessionHandle.PreferencesObserver and com.documentum.fc.client.impl.collection.CollectionHandle.PreferencesObserver classes are designed to apply changes of dfc.diagnostics.resources.enable DFC preference in runtime, but the dfc.diagnostics.resources.enable preference is marked as non-dynamic – looks like a stupid mistake, doesn’t it? In order to eliminate this gap I have created another one jsp: