ADx 2.6.281 (24/06/2021) Patch Release Notes

This is a patch release to ADx 2.6. Here's a list of bug fixes (see bellow) and new features:

• merge-templates API is configurable to apply templates only on specified contents

{
  "_type": "tribefire.adx.model.content.service.v1.request.conversion.merge.MergeTemplatesByIds",
  "contentIds": [
    "MY_CONTENT",
    "MY_TEMPLATE_NOT_TO_BE_USED",
    "MY_TEMPLATE_TO_BE_USED"
  ],
  "resultAction": "NEW_CONTENT",
  "targetName": "MyTargetName",
  "templateSpecifications": [
    {
      "_type": "tribefire.adx.model.content.service.v1.request.conversion.merge.TemplateSpecification",
      "contentIds": [
        "MY_TEMPLATE_TO_BE_USED"
      ],
      "mapRecord": {
        "_type": "com.braintribe.model.record.MapRecord",
        "_id": "3",
        "values": {
          "_type": "flatmap",
          "value": [
            "myKey",
            "myValue"
          ]
        }
      }
    }
  ]
}

• merge-templates API converts all known file types to pdf before merging
• beta version of copy folder structure added - don't use it in production environments

Java Version

This release was tested with JDK 11 JDK-11.0.11-zulu11.48.21.

Changes in actual version

Nothing has been removed since previous release.

Changes in upcoming versions

Nothing is going to be removed in future release.

Runtime Properties and Configuration changes

No runtime properties have been added, changed or removed in this release.

List of New Features and Improvements

Issue	Priority	Summary Description
AD-2454	Major	Copy Folder structure - beta version

Bug Fixes

Issue	Priority	Summary Description
AD-2447	Critical	Allow merge template of non pdf documents - make it more lenient

Updating Conversion and ADx

For information on how to update previously installed Conversion and ADx, see the following:

• Updating Conversion
• Updating ADx

Known Issues

Below you can find a list of problems we're still working on.

Known Issues ADx

Ticket	SEVERITY	Description
https://jira.braintribe.com/browse/AD-321	CRITICAL	Add missing indices
https://jira.braintribe.com/browse/AD-348	MAJOR	ADx Admin: Repository Modification-Status not updated on Update
https://jira.braintribe.com/browse/AD-1898	MAJOR	Min and Max length metadata not respected on initial upload
https://jira.braintribe.com/browse/AD-342	MINOR	Hibernate warnings in the log files
https://jira.braintribe.com/browse/AD-341	MINOR	Java warnings during for Java 9 and later
https://jira.braintribe.com/browse/AD-311	MINOR	Oracle - DbLockManager prints Oracle constraint message

Reimporting an Existing Repository Requires UI Reload

In some cases, when reimporting an existing repository, repository properties are not rendered correctly. To make sure properties are rendered correctly, refresh your browser after each import.

Cannot migrate legacy contents simultaneously

Due to cache database being shared between repositories, it's not possible for now to run multiple migration jobs from a single legacy repository at the same time. You need to wait for the previous migration to finish before running a new one.

Min and Max length metadata not respected on initial upload

String length checks are only applied when values are updated but not on the initial upload.

Known Issues Conversion

Ticket	SEVERITY	Description
https://jira.braintribe.com/browse/AD-338	CRITICAL	Introduce roles for conversion
https://jira.braintribe.com/browse/AD-337	MAJOR	Make TF Conversion workbench consistent to ADx
https://jira.braintribe.com/browse/EXTDOCS-71	MINOR	Fix wrong encoding on opening resource in Browser

Minor Warnings

StatusLogger Error

The following error currently appears in ADx console output. It doesn't affect ADx functionality or performance.

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
  Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.

Tomcat Shutdown Warning

The following warning is sometimes thrown by Tomcat when stopping the service:

./tribefire-console-stop.sh
...
Tomcat did not stop in time.
PID file was not removed.
To aid diagnostics a thread dump has been written to standard out.
Tribefire Host stopped.

This happens when shutdown takes longer than Tomcat expects. Shutdown may take several minutes, which will result in this message being printed out. This warning could appear on both Conversion and ADx.

Java Warnings

When using Java 9 or later, the following warning may appear in application logs and also during installation procedure:

WARNING: An illegal reflective access operation has occurred
WARNING : Illegal reflective access by com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 (file:/path/to/instant-type-weaving-1.0.28.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Ticket: https://jira.braintribe.com/browse/AD-341

Hibernate Warnings

The log files may contain Hibernate-related warnings. They can be identified based on the fully qualified class which starts with org.hibernate, as in:

WARNING org.hibernate.tuple.entity.EntityMetamodel 'HHH000084: Entity [com.braintribe.model.user.User] is abstract-class/interface explicitly mapped as non-abstract; be sure to supply entity-names' [TribefireServices-2.0:tribefire-services#initialize,ApplicationLoader:/tribefire-services#initialize]

Ticket: https://jira.braintribe.com/browse/AD-342

These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.