Page 1 of 1

Transformation fails after upgrading to v22.1

Posted: Wed Sep 30, 2020 9:12 pm
by Carl
I just upgraded to v22. I preserved what I thought were all my customizations, but when try to create a PDF using XSL-FO, I get this fatal error:

Code: Select all

System ID: /home/clum/repos/docs-cust/PHEMI_Central/phemi_central_spitfire_ui.ditamap
Scenario: DITA Map PDF - based on XSL-FO - Copy
Input file: /home/clum/repos/docs-cust/PHEMI_Central/phemi_central_spitfire_ui.ditamap
Engine name: DITA-OT
Severity: fatal
Description: Transformation failed. org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider ro.sync.xml.transformer.dita.remote.RelaxDefaultsDITARemoteMapsParserConfiguration could not be instantiated: java.awt.HeadlessException
It's probably something quite simple that I missed copying over, but I have no idea based on this error message. :?

Re: Transformation fails after upgrading to v22.1

Posted: Thu Oct 01, 2020 7:19 am
by Radu
Hi Carl,

Please write an email to and give us more details:

- After the transformation fails there should be a "DITA-OT" console tab at the bottom of Oxygen containing all the logging received from the build process. Can you save the entire log contents to a file and attach it to the email?
- What precise Oxygen build ID do you have? In the Oxygen main menu Help->About dialog there should be some information like <oXygen/> XML Editor 22.1, build 2020061102. I'm interested in the build number
- Are you running Oxygen on Linux or on Mac? If you restart your computer can you still reproduce the problem?
- In the transformation scenario you are using in the "Advanced" tab there is a "Java Home" setting. Did you change that to point to a custom Java distribution? Can you also attach to the email a screenshot with this dialog?


Re: Transformation fails after upgrading to v22.1

Posted: Fri Oct 09, 2020 1:17 pm
by Radu

As an update we found out the problem could be reproduced for any Oxygen 22.1 running with Java 14. We updated our Oxygen 22.1 installation kits on the web site to fix the problem: