Transformation Test fails on 6.2

[AFaust]

BUG

Expected behavior

Using the /alfresco/s/ootbee/admin/test-transform tool and testing the transformation from one file extension (type) to another shows a report detailing the supported transformations and order in which they would be attempted / prioritised, as well as a summary of execution duration for the transformation of (potentially) prepackaged test files.

Actual behavior

Executing the transform test results in a java.lang.IllegalArgumentException: URI is not hierarchical being displayed in the popup. Debugging deeper into the Java code, the URL affected is jar:file:/usr/local/tomcat/webapps/alfresco/WEB-INF/lib/alfresco-repository-7.134.1.jar!/quick/quick.odt which points to a file packaged in default Alfresco for specifically testing transformations.

Steps to reproduce the behavior

• access the /alfresco/s/ootbee/admin/test-transform tool
• select odt as source and pdf as target file type in the "Test transform" section, making no other selection
• click the "test" button

Additional details (analysis so far, log statements, references, etc.)

Listing all supported transformations from odt to pdf shows an empty list despite no messages during startup that T-engines were unavailable or transformations were not supported for any reason. I wonder if the new Transformation framework even works properly with the Transform tooling at all, or is essentially broken and in need of being replaced on Alfresco 6.0/6.1 and onwards.

Tell us about your environment

Alfresco 6.2.0-ga (default Alfresco Docker image) on Win 10, using Docker Compose deployment with all supported transformer containers for the Local Transform variant of the RenditionService2 transformation framework.

[AFaust]

Based on some information from a customer environment (6.1 and 6.2) this may not be a general issue and may be dependent on some as-of-yet unknown environment configuration / aspect.

[AFaust]

This issue is a general issue on Alfresco 6.2 with JDK 11. It is due to a jar:file:/ URI string not being parsed to a URI object with the internal path set to the path of the file. This may be related to how classloader / JAR contained files work in that Java version, but it cannot be fixed by the Order of the Bee Support Tools addon itself. As a result, this issue will be closed. The test transform action in the Transformations tool simply cannot be made to work for this ACS and Java version combination.