Backwards compatibility in Content Delivery

A list of changed behavior in Content Delivery.

TCDL tag handling changed to handle processing of TCDL tags for Tridion Docs
As of SDL Tridion Sites 9, handling the two different versions of the tcdl:Link tag (one for Tridion Sites, another for Tridion Docs) has caused the following API changes:
  • The com.tridion.tcdl.TagHandlerRegistry and com.tridion.tcdl.DefaultTagSet now examine the attributes of the tcdl:Link to determine which tag handler to invoke.
  • The BinaryLink(), PageLink() and ComponentLink() each have a new signature with two parameters: first a String parameter for the namespace ("ish" or "tcm"), then the existing int parameter for the Publication ID.
Context Service WAR file dropped

As of SDL Web 8.5, the Context Service is no longer available as a Java/JSP Web application.

WAR implementations of microservices no longer shipped

As of SDL Web 8.5, all Java/JSP Web application-based microservices no longer ship with the product release. If you still want to maintain this deprecated and actively discouraged setup, you must contact SDL Customer Support.

Content Deployer Processor extensions no longer supported

As of SDL Web 8.5, the product no longer supports extending the Processor of the Content Deployer to perform custom processing. You can, however, still create custom Modules for Content Deployer.

Some cache statistics dropped

As of SDL Web 8.5, a number of cache statistics for Context Engine are no longer available following a move to switch to Ehcache 3.

Tag Libraries now follow the Servlet 2 specifications

As of SDL Web 8.5, Java/JSP Tag Libraries have been updated to follow the Servlet 2 specification. It follows from this that you no longer need to copy Tag Libraries to the WEB-INF/ folder of your Java/JSP Web applicaiton, but have them load from within the artifact JAR files themselves. The impact for the implementer is that they need to modify their tag library reference (in the uri attribute) within JSP pages, and remove references to Tag Libraries from the Web application definition file, web.xml.

Search Filter API dropped

Having been deprecated already as of SDL Tridion 2011, the Search Filter API is dropped as of SDL Web 8. Refer to your previous documentation for guidelines on how to turn your Search Filter API calls into Content Broker Query API calls.

Transformation of Content Broker configuration dropped

Having been deprecated already as of SDL Tridion 2011, the Content Broker configuration file is no longer supported as of SDL Web 8. Refer to your previous documentation for guidelines on how to turn your Content Broker configuration into a Storage Layer configuration, and how to handle any custom home classes you may not yet have updated or reimplemented.

Classic ASP API and ASP.NET API for SDL Tridion 5.3 SP1 and earlier dropped

Having been deprecated already as of SDL Tridion 2009, support for the classic ASP API, as well as for the ASP.NET API used in SDL Tridion 5.3 SP1 and earlier, is dropped as of SDL Web 8. Refer to your previous documentation for guidelines on how to turn you classic API calls and/or old ASP.NET API calls in to API calls to the new ASP.NET API.

Support for inline code generation dropped

Having been deprecated already as of SDL Tridion 2009, support for generating inline code from any Content Delivery API (whether Java or .NET) dropped as of SDL Web 8. Refer to this documentation to learn how to produce Server Controls (.NET) or Tag Libraries (Java) instead.

User Generated Content (UGC) interface SpamFilter dropped

The SpamFilter interface, which was a part of User-Generated Content in SDL Tridion 2011 SP1, after being deprecated, has been dropped in favor of the Validator interface.