ref #10089 adapt json mapping to new TypeDesignationSet handling (cont.)

[cdmlib.git] / cdmlib-remote / src / main / resources / eu / etaxonomy / cdm / remote / json / jsonConfigurations.xml

diff --git a/cdmlib-remote/src/main/resources/eu/etaxonomy/cdm/remote/json/jsonConfigurations.xml b/cdmlib-remote/src/main/resources/eu/etaxonomy/cdm/remote/json/jsonConfigurations.xml
index d2d21251b0097524cfe5a9bde0c7499f27db4c15..af7a978915b37e80fd0501ca500446eb4470091f 100644 (file)
--- a/cdmlib-remote/src/main/resources/eu/etaxonomy/cdm/remote/json/jsonConfigurations.xml
+++ b/cdmlib-remote/src/main/resources/eu/etaxonomy/cdm/remote/json/jsonConfigurations.xml
@@ -536,7 +536,7 @@
             <bean class="eu.etaxonomy.cdm.remote.json.processor.value.MapJSONValueProcessor" />
         </entry>
         <entry key="eu.etaxonomy.cdm.api.service.name.TypeDesignationSet">
-            <bean class="eu.etaxonomy.cdm.remote.json.processor.value.MapJSONValueProcessor" />
+            <bean class="eu.etaxonomy.cdm.remote.json.processor.value.TypeDesignationSetValueProcessor" />
         </entry>
         <entry key="eu.etaxonomy.cdm.common.URI">
             <bean class="eu.etaxonomy.cdm.remote.json.processor.value.URIJSONValueProcessor"/>