Take a DocumentTypeManager instead of DocumentmanagerConfig

- The manager is now set up as a component in the config model.

1 files changed, 2 insertions, 2 deletions

diff --git a/docproc/src/main/java/com/yahoo/docproc/jdisc/DocumentProcessingHandler.java b/docproc/src/main/java/com/yahoo/docproc/jdisc/DocumentProcessingHandler.java
index a949ec5ecf3..3b31b0447a3 100644
--- a/docproc/src/main/java/com/yahoo/docproc/jdisc/DocumentProcessingHandler.java
+++ b/docproc/src/main/java/com/yahoo/docproc/jdisc/DocumentProcessingHandler.java
@@ -102,7 +102,7 @@ public class DocumentProcessingHandler extends AbstractRequestHandler {
                                      ComponentRegistry<AbstractConcreteDocumentFactory> docFactoryRegistry,
                                      ChainsConfig chainsConfig,
                                      SchemamappingConfig mappingConfig,
-                                     DocumentmanagerConfig docManConfig,
+                                     DocumentTypeManager documentTypeManager,
                                      DocprocConfig docprocConfig,
                                      ContainerDocumentConfig containerDocConfig,
                                      Metric metric) {
@@ -110,7 +110,7 @@ public class DocumentProcessingHandler extends AbstractRequestHandler {
              documentProcessorComponentRegistry, docFactoryRegistry,
                 new DocumentProcessingHandlerParameters()
                      .setMaxNumThreads(docprocConfig.numthreads())
-                     .setDocumentTypeManager(new DocumentTypeManager(docManConfig))
+                     .setDocumentTypeManager(documentTypeManager)
                      .setChainsModel(buildFromConfig(chainsConfig)).setSchemaMap(configureMapping(mappingConfig))
                      .setMetric(metric)
                      .setContainerDocumentConfig(containerDocConfig));