Release Notes

“Web framework pluggability” has been introduced in version 3.0 of the Java Servlet Specification (see Java Servlet 3.0 Specification). This enables the following, for example:

• Modularization of web.xml or
• Configuration of components via Java annotations.

Globally, “web framework pluggability” is activated in FirstSpirit using the WEBAPP_ENABLE_PLUGGABILITY_FEATURES_DEFAULT parameter (default value “true”) in the fs-server.conf file (see Area: Web Applications chapter (fs-server.conf)). With this setting, all Java classes are scanned for annotations upon deployment.

If the function is not required, it can be deactivated globally or for individual web applications so that deployment on the web server does not take longer than necessary. The “pluggability” selection field is used for configuring and deactivating individual web applications; this applies to either global web applications (FirstSpirit ServerManager, Server properties/Web applications) or the web components of a project (FirstSpirit ServerManager, Project properties/Web components).

As of FirstSpirit 2021-01, pluggability detection for web applications has been improved. Pluggability is now guaranteed to be activated automatically if at least one web component in a web application requires pluggability. The pluggability of a web component is affected by the metadata-complete and absolute-ordering attributes.

The new behavior ensures that incorrect configurations result in fewer conflicts. Where necessary, this also overwrites the explicit “Inactive” setting for pluggability in ServerManager (see Server properties/Web applications).

FirstSpirit 2021-01 supports the following module versions for “FirstSpirit Content Experience Tools”:

* These modules require FirstSpirit 2020-03 or higher from this version.

The “variant” principle of FirstSpirit Content Experience Tools allows for different variants of a fragment. A variant dimension of a fragment may be the language, for instance.
Variants are implemented from a technical perspective using a <CMS_GROUP> form with the identifier editions in the metadata template. In this case, the language variable is what enables the editor to select the language and the (language-dependent) content to be stored.

The FS_INDEX component can be used to create new fragments in a remote project, for example. The current variant dimension is now always preselected in the latest release, e.g.

Another variant dimension can be selected in this dialog if necessary.

The new fragment is created in the remote project that is specified via the remote attribute in the PROJECT tag of the applicable FS_INDEX component.
If the variant dimensions defined by means of editions in the source project and target project are different from one another, a random target project dimension is preselected.

FS_INDEX code example:

<FS_INDEX name="fragments" useLanguages="no">
     <LANGINFOS>
       <LANGINFO lang="EN" label="Select / create contact person"/>
       <LANGINFO lang="*" label="Kontakt auswählen / erstellen"/>
     </LANGINFOS>
     <SOURCE name="FirstSpiritFragmentAccess/FSFAConnector">
       <PROJECT remote="fragments">
         <CATEGORY uid="contacts"/>
       </PROJECT>
     </SOURCE>
</FS_INDEX>

The JAXB package javax.xml.bind (Java Architecture for XML Binding) has been removed as of Java 11. When upgrading FirstSpirit modules to Java 11, module developers must now ensure that modules requiring this resource provide it themselves. For this purpose, the ScheduleTaskApplication interface now supports the integration of a JAXB library locally within a module.

The multisite management functions “FirstSpirit ContentTransport” and “FirstSpirit CorporateContent” make it possible to transport project content and properties from a source project to a target project. In the case of both functions, stability and performance have been improved when transporting large data volumes. It is now possible to transport large data volumes with little memory usage. The improved behavior also has an impact on importing/exporting zip files via the corresponding context menu functions in SiteArchitect.

For more information on the functions referred to above, see:

• Module documentation on “FirstSpirit CorporateContent”, “CorporateContent” and “ContentTransport” chapters (PDF)
• Documentation on “FirstSpirit SiteArchitect”, “Special context menu functions” chapter

The new nonDisplayedSectionsRendering configuration parameter can be used to generate the output of hidden sections.

$CMS_SET(#global.json.nonDisplayedSectionsRendering, true)$

If the value is set to “true”, an additional “displayed” attribute is generated for each section.
If the value is set to “false” (default value), this attribute is not generated.

If this option is set to “true” in the page template for the global setting, for example, the “displayed” attribute is then used to show the language-dependent setting for each section, which determines whether the section is to be displayed or not.

Example:

Note: If the configuration parameter is not set, sections that do not have a check mark will not be output at all. Setting the parameter not only adds additional attributes during output, but also generates hidden sections.