CoreMedia Content Cloud v12 Upgrade Guide / Version 2404
Table Of ContentsChanges only necessary when you imported component XML files before
When you have imported the component XML files, you now have to import the configuration classes.
In the course of migrating from Spring XML to Java configurations, some XML files were removed in favor of their replacement Java Spring configuration classes. The details can be found below:
removed bpbase-links-postprocessor.xml (import BlueprintLinksPostprocessorsConfiguration instead)
removed bpbase-context-finder-services.xml (import NavigationContextFinderConfiguration instead)
removed handler-services.xml (import CaeHandlerServicesConfiguration instead)
removed link-services.xml (import CaeLinkServicesConfiguration instead)
removed user-services.xml (import UserServicesConfiguration instead)
removed cap-xliff-service.xml (import CapXliffConfiguration instead)
removed mimetype-service.xml (import MimeTypeServiceConfiguration instead)
removed com.coremedia.cap.test.xmlrepo.XmlRepoResources (import Java configuration classes instead)
In the course of updating from spring boot 2.7 to 3.2 a number of configuration XML files and configuration classes had to be adjusted:
Bean
translate.xliff.translatableExpressions
provided by classcom.coremedia.translate.item.TranslatablePredicateConfiguration
was renamed totranslateXliffTranslatableExpressions
com.coremedia.blueprint.studio.topicpages.rest.CustomTopicPagesConfiguration
was renamed toCustomTopicPagesAutoConfiguration
com.coremedia.blueprint.analytics.elastic.rest.ESALXStudioConfiguration
was renamed toESALXStudioAutoConfiguration
com.coremedia.blueprint.taxonomies.TaxonomyConfiguration
was renamed toTaxonomyAutoConfiguration
com.coremedia.blueprint.studio.rest.taxonomies.TaxonomyStudioConfiguration
was renamed toTaxonomyStudioAutoConfiguration
com.coremedia.blueprint.studio.rest.intercept.InterceptorsStudioConfiguration
was renamed toInterceptorsStudioAutoConfiguration
XML configuration file
com/coremedia/blueprint/common/multisite/translation-config.xml
was removed without replacementXML configuration file
META-INF/coremedia/studio-in-memory-cap-list.xml
was removed without replacementXML configuration file
META-INF/coremedia/es-alx-common.xml
was removed without replacementXML configuration file
META-INF/coremedia/es-alx-contentbeans.xml
was removed without replacementXML configuration file
META-INF/coremedia/es-alx-retrieval.xml
was removed without replacementXML configuration file
META-INF/coremedia/caefeeder-blueprint.xml
was removed without replacementXML configuration file
META-INF/coremedia/caefeeder-services.xml
was removed without replacementXML configuration file
META-INF/coremedia/livecontext-contentfeeder.xml
was removed without replacementXML configuration file
META-INF/coremedia/elastic-worker.xml
was removed without replacement
The CoreMedia Component Loader is deprecated in favor of Spring Boot auto configurations. Many Spring component XML files have been converted to Spring Boot auto configuration classes. Several non-component Spring XML files have been converted to Spring configuration classes in that course. Also, existing configuration classes have been renamed and component properties files have been renamed to ordinary properties files. The detailed changes are listed below.
Migration from CoreMedia Component Loader to Spring Boot auto configurations:
component-lc-asset.xml —> LcCaeAssetAutoConfiguration
component-elastic-social.xml → ElasticSocialCaeAutoConfiguration
component-alx-cae.xml → AlxCaeAutoConfiugration
component-am-cae.xml → AMCaeAutoConfiguration
component-blueprint-cae.xml → CaeBaseComponentAutoConfiguration
component-corporate-cae.xml → CorporateCaeAutoConfiguration
component-alx-google-cae.xml → AlxGoogleCaeAutoConfiguration
component-personalization.xml → P13NCaeAutoConfiguration
component-p13n-preview-cae.xml → P13NPreviewCaeAutoConfiguration
component-alx-p13n-cae.xml → P13NAlxCaeAutoConfiguration
component-cae.xml → CaeComponentAutoConfiguration
component-cap-client.xml → CapClientComponentAutoConfiguration
component-base.xml → CustomizerAutoConfiguration
Migration of Spring XML to Spring Java configuration:
livecontext-handler-interceptors.xml → LcCaeInterceptorsConfiguration
component-lc-elastic-social.xml → LcElasticSocialCaeAutoConfiguration
component-lc-p13n-cae.xml → LcP13NCaeAutoConfiguration
component-lc-preview-cae.xml → LcPreviewCaeAutoConfiguration
component-lc-p13n-preview-cae.xml → LcP13NPreviewCaeAutoConfiguration
livecontext-preview-links.xml → LcPreviewCaeLinkConfiguration
livecontext-preview-handler-interceptors.xml → LcPreviewCaeInterceptorsConfiguration
personalization-context.xml → P13NCaeContextConfiguration
p13n-preview-cae-context.xml → P13NPreviewCaeContextConfiguration
personalization-collection.xml → ContextCollectionConfiguration
Removal of Spring XML configuration files:
removed lc-asset-handlers.xml (import LcCaeAssetHandlersConfiguration instead)
removed blueprint-i18n.xml (import com.coremedia.blueprint.cae.config.BlueprintI18nCaeBaseLibConfiguration instead)
removed blueprint-l10n.xml (import com.coremedia.blueprint.cae.config.BlueprintL10nCaeBaseLibConfiguration instead)
removed blueprint-search.xml (import com.coremedia.blueprint.cae.config.BlueprintSearchCaeBaseLibConfiguration instead)
removed blueprint-richtextfilters.xml (import com.coremedia.blueprint.cae.config.BlueprintRichtextFiltersConfiguration instead)
removed livecontext-validation.xml (import LcCaeValidationConfiguration instead)
removed livecontext-links.xml (import CommerceLinkConfiguration instead)
removed livecontext-fragment.xml (import LcCaeFragmentConfiguration instead)
ec-cae-lib.xml was resolved. Its imports were transferred to CorporateCaeAutoConfiguration and LcCaeAutoConfiguration.
removed livecontext-preview-hybrid.xml. It only contained a customizer, which was migrated to LcPreviewCaeAutoConfiguration.
removed blueprint-links.xml (import com.coremedia.blueprint.cae.config.BlueprintLinksCaeBaseLibConfiguration instead)
removed personalization-interceptors.xml (import com.coremedia.blueprint.personalization.config.P13NInterceptorsConfiguratio instead)
removed p13n-preview-cae-context-.xml (import
com.coremedia.blueprint.personalization.preview.config.P13NPreviewCaeContextConfiguration instead)removed bpbase-sitemodel.xml (import com.coremedia.blueprint.base.multisite.BlueprintMultisiteModelConfiguration instead)
removed view-development-services.xml (import com.coremedia.objectserver.view.config.CaeViewDevelopmentServicesConfiguration instead)
removed view-error-services.xml (import com.coremedia.objectserver.view.config.CaeViewErrorServicesConfiguration instead)
removed customizer-services.xml (import com.coremedia.springframework.customizer.CustomizerConfiguration instead)
Renamed Spring Java configurations:
LcCaeAssetConfiguration → LcCaeAssetHandlersConfiguration
CaeBaseComponentConfiguration → CaeBaseComponentAutoConfiguration
LiveContextPreviewCaeConfiguration → LcPreviewCaeAutoConfiguration
CapClientComponentConfiguration → CapClientComponentAutoConfiguration
Miscellaneous:
removed component-blueprint-cae.properties as it only contained
properties set to the default values or commented out properties.removed abstract bean 'storeContextInterceptor’ as there is no such thing as abstract beans in Java config.
removed component-livecontext.properties → livecontext.properties (imported in LcCaeAutoConfiguration)
migrated bean definitions from CaeComponentConfiguration to CaeComponentAutoConfiguration and removed it
removed com.coremedia.personalization.context.collector.LicenseHelper from public API
removed com.coremedia.cms:cae-util module. Consequently, uapi-services.xml and CaeUtilConfiguration were removed as well. The beans were migrated to ContentBeanServicesConfiguration.