The new release offers the new ExtensionPoint CustomFilterQuery in order to provide custom filter queries by a plugin.

The introduction of this new extension point made it necessary to move the existing code base for the search into Blueprint Base. Thus, this is considered a breaking change!

However, if search related code in Blueprint was not adapted in any way, this change does not affect an update.

If the former search extension was adapted, the code changes should be moved into an own extension or a plugin depending on the grade of customization. Changes in the search-schema and custom filter queries can easily be moved into a plugin. This has the advantage, that future changes within headless-server should have lesser impact regarding changes in the public API, because ExtensionPoints are considered more stable and version independent.

Extensions which depend on the former search extension must now depend on headless-server instead.

Self implemented custom filter queries using the former HeadlessSearchConfiguration must be provided now as a Spring bean, using the new ExtensionPoint CustomFilterQuery. Examples can be found in the updated headless manual.

If the former search-schema was changed, the now provided search-schema can be disabled, setting configuration parameter 'caas.search.loadSearchSchema=false'. Instead provide your own schema using the plugin mechanism for resource files or provide the schema file using an extension.

If Java code of the former search extension was replaced, e.g. SpringBeans, you have to use Spring annotations like @Customize to override the provided SpringBeans. Alternatively it is possible to disable the headless-search completely and provide an own implementation of the search as an extension.

(CMS-20367)