Release Notes / Version 10.2107
Table Of Contents
Some CAE modules underwent structural refactoring, which possibly requires some dependency and import changes in your project code. (All artifacts mentioned here have the groupId
com.coremedia.cms
.)
cae-linkservices-api
andcae-linkservices-impl
have been merged tocae-linkservices
.cae-handlerservices-api
andcae-handlerservices-impl
have been merged tocae-handlerservices
.cae-viewservices-api
andcae-viewservices-impl
have been merged tocae-viewservices
.cae-contentbeanservices-api
andcae-contentbeanservices-impl
have been merged tocae-contentbeanservices
.
The dependency management for
cae-handlerservices
and
cae-viewservices
has been moved from
middle-core-bom
to
cae-core-bom
. Thus, you must possibly add
cae-core-bom
to your
<dependencyManagement>
. In most cases the
cae-core-bom
entry will already be there, since these modules should not be used outside the CAE application anyway.
com.coremedia.objectserver.web.HttpError
has been moved from
cae-util
to
cae-common
, managed in
cae-core-bom
.
com.coremedia.objectserver.view.ViewUtils
has been split. The most popular methods
getBaseUri
,
setBaseUri
and
getParameters
have been extracted to the new class
com.coremedia.objectserver.request.RequestUtils
, which is available in the
cae-request-util
artifact, managed in
middle-core-bom
.
com.coremedia.objectserver.web.taglib.TemplateHelper
has been moved from
cae-viewservices-api
to
com.coremedia.objectserver.web.template.TemplateHelper
in
cae-linkservices
.
com.coremedia.objectserver.web.ModelAwareViewResolver
has been moved from
cae-viewservices-api
to
cae-handlerservices
.
The module
cap-objectserver
has been deleted. It was empty, its only "feature" was the pom with some historically motivated dependencies. Just depend directly on the modules you really use in your code, instead of inheriting an arbitrary set of dependencies from
cap-objectserver
.
(CMS-17072)