Update the extended operation config manager so that it will register any
appropriate supported controls or supported extensions in the case where an
existing extended operation handler had been disabled when the server started
but was then enabled with the server running. This was a case that was
previously overlooked in issue #597.
| | |
| | | } |
| | | |
| | | |
| | | // If the extended operation handler defines any supported controls and/or |
| | | // features, then register them with the server. |
| | | Set<String> controlOIDs = handler.getSupportedControls(); |
| | | if (controlOIDs != null) |
| | | { |
| | | for (String oid : controlOIDs) |
| | | { |
| | | DirectoryServer.registerSupportedControl(oid); |
| | | } |
| | | } |
| | | |
| | | Set<String> featureOIDs = handler.getSupportedFeatures(); |
| | | if (featureOIDs != null) |
| | | { |
| | | for (String oid : featureOIDs) |
| | | { |
| | | DirectoryServer.registerSupportedFeature(oid); |
| | | } |
| | | } |
| | | |
| | | |
| | | handlers.put(configEntryDN, handler); |
| | | return new ConfigChangeResult(resultCode, adminActionRequired, messages); |
| | | } |