CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of Contents
The schema definition for tests using the XML Repository has been moved
from Blueprint Base module
com.coremedia.blueprint.base:bpbase-test-util
to Blueprint module
com.coremedia.blueprint:test-util
.
All corresponding tests in Blueprint got their references adapted from the old artifact to the new artifact:
was:
classpath:com/coremedia/blueprint/base/testing/blueprint-doctypes-xmlrepo.xml
is:
classpath:com/coremedia/testing/blueprint-doctypes-xmlrepo.xml
The new artifact contains the very same definitions as the original XML-Repository schema.
The old artifact is still available, but it is deprecated and will be removed in upcoming versions.
Upgrade: Changes will be automatically applied by Git update to existing tests. For custom tests, it is strongly recommended updating the reference to the new content-type definitions.
General Note: The motivation for moving the definition is, that if you customized your content-type definitions for your project, you may have experienced especially CAE ContentBean tests to struggle with insufficient definitions. Thus, by nature of the existing tests you may have been forced providing a custom schema. With this change, this will be feasible without the need to extract the definitions from JAR files.
In general, we recommend providing a custom schema for each test with the specific content-types and properties required by that test. This increases maintainability. In addition to that, you may want to use standard content-type definitions in the same format supported by the Content Server. How to do that, and for more information read the corresponding JavaDoc:
XmlUapiConfig.Builder.withContentTypes(...)
is the method
to use to refer to content-type definitions as supported by the
Content Server.