Details
-
Improvement
-
Status: Closed
-
High
-
Resolution: Fixed
-
None
-
None
-
None
Description
The channel manager interface is currently accessed directly as a java class by the channel manager user interface. This requires the hst api & commons jars to be on the shared classpath.
The CMS can also access HST rest services; those are preferred to the direct class approach. Ideally, the same jax-rs annotated interface is used in the cms to deserialize the responses sent by the (identical) jax-rs service in the HST. Such a solution is already in place for the document url service (view in channel dropdown).
Attachments
Issue Links
- causes
-
HSTTWO-2113 ChannelDocument should be serializable
- Closed
-
HSTTWO-2115 Channel should be serializable
- Closed
-
HSTTWO-3323 Make sure JCR eventListeners registered via HST Spring beans get their methods invoked with HST webapp classloader
- Closed
- includes
-
CMS-6280 Apply code comments from HSTTWO-2049
- Closed
-
ARCHE-215 Adapt archetype dependencies for new Channel Manager REST Service
- Closed
- relates to
-
CMS-5870 Use the jax-rs channel manager service in the channel manager user interface
- Closed