Updated (embedded) Tomcat to 9.0.73

Embedded Tomcat has been updated to version 9.0.73 (see Changelog Tomcat 9.0.73 and predecessors) to prevent known vulnerabilities.

(CMS-22877)

Workflow Server Health Check for UAPI Connection

Workflow Server's health check (accessible through actuator health) did not reflect a working connection to the Content Management Server and could show healthy, even if the connection to the Content Management Server was broken and the Workflow Server thus partly inoperable. This is now fixed and connection status will be reflected properly.

(CMS-22659)

XLIFF Import: Markup in Structs Support Enhanced

XLIFF Import of Markup in Structs may have failed, reporting an invalid property value. This got caused by Markup nodes in Struct, where only the Markup value holds grammar information.

This got fixed in that way, that if no other information is available, a fallback to CoreMedia Rich Text 1.0 grammar is applied to the imported Markup node.

(CMS-22528)

RichtextInStructTranslatablePredicate: NullPointerException Fixed

RichtextInStructTranslatablePredicate, used to mark all Struct nodes with CoreMedia RichText 1.0 Grammar as translatable failed with NullPointerException if Markup nodes exist without grammar set at Struct node.

The robustness has been increased: Struct Markup nodes without grammar set at node are now ignored, not being marked as translatable.

Note, that having this, nodes without grammar declared at Struct, but with Markup values having a grammar set, are ignored, too. A corresponding issue exists, to address this, but this requires more fundamental changes, as TranslatablePredicate instances do not have access to the value of a property, yet.

Thus, for best support by CoreMedia Multi-Site feature, it is recommended to set the grammar at Struct Markup nodes always.

(CMS-22527)

Content Feeder Event Handling Robustness

The Content Feeder's event handling has been made more robust, so that it can recover from temporary connection problems to the Content Server after initial feeding has completed. Before this change, the Content Feeder would stop after connection problems, and log an error like "An unexpected error occurred while processing a change". This change now avoids the need to restart the Content Feeder in such cases.

(CMS-8763)