Details
-
Bug
-
Status: Closed
-
Top
-
Resolution: Fixed
-
None
-
None
-
None
-
1
-
Turing Sprint 158
Description
Since spring addon module support, it is not needed any more that template-composer-rest.xml and hst-cms-rest.xml are present in META-INF.hst-assembly.overrides. If they are missing, it is really hard to find out why the channel mngr is not working. A more fundamental problem is that the template-composer-rest.xml and hst-cms-rest.xml include SpringComponentManager-rest-jackson.xml. If some bean in SpringComponentManager-rest-jackson.xml is overridden for a content jaxrs feature (for example customJaxrsRestEntityProviders), then most likely the last file that includes SpringComponentManager-rest-jackson.xml will override the settings. Hence, for the template composer (CM) and cms rest modules, we should include their own rest-jackson beans which can be overridden separately
Attachments
Issue Links
- causes
-
HSTTWO-4043 Support to use Spring addon beans in downstream projects as well in spring wiring
- Closed
-
HSTTWO-4044 Make sure pageComposerPropertyPresentationFactories is available via the core hst component mngr so downstream projects can access it
- Closed
-
HSTTWO-4046 Make sure jaxrsHstConfigCxfServerFactoryBean is available via the core hst component mngr so downstream projects can access it
- Closed
- includes
-
ARCHE-535 Remove the from now on redundant hst-cms-rest.xml and template-composer-rest.xml
- Closed
- is awaited by
-
HSTTWO-3639 Overriding customJaxrsRestEntityProviders does not work
- Closed
- relates to
-
ESSENTIALS-1043 Improve REST API setup tool to show URL for Content REST API and not log stacktraces for 404s
- Closed
-
HSTTWO-4050 HST Spring addon module support for explicitly defining a parent module
- Closed
-
HSTTWO-4045 Make AbstractConfigResource#getPageComposerContextService non final because downstream project that extend from AbstractConfigResource may want to override it to return an object from a Supplier
- Closed