Thanks Radu.
I set in the catalog and now transformations work.

Pablo

Thanks, Radu, I know. My catalog-dita.xml already contains the nextCatalog entry to my specialized topic types. This is precisely why validation does work. But how come validation works, but transformation does not? It seems as if Oxygen is following the PUBLIC ID through the XML catalog to find the...

Hi! I am trying to run DITA transformation scenarios on DITA XML files. The XML files are based on customized versions of topic/concept/task/reference, not on the standard DITA-OT's. To make Oxygen aware of these customizations, I created an XML catalog, and added the catalog entry in $OXYGEN/framew...

Hey Radu. I copied the references to libraries from the working DITA Map XTHML scenario into a duplicate of the Ant Transformation scenario, which I used to run apiRef's run-ant.xml file. I got past the "XMLGrammarPool" error, but got a NullPointerException further ahead. This is my transf...

Thanks, Radu. I am using the DITA-OT that came with Oxygen 13. I made some (working) modifications to it so I intend to reuse it. I did not make any changes to the transformation scenario's advanced options. Just now I noticed that the DITA Map XHTML transformation scenario does not fail. It only fa...

Radu, I set the configuration you suggested. I am under SVN so I can see my extensions were added to catalogs and dita2xhtml.xsl. However, I cannot get to try it out since I get Oxygen XML Editor 14\frameworks\dita\DITA-OT\build_preprocess.xml:38: java.lang.NoClassDefFoundError: org/apache/xerces/xn...

Hi Radu, I have installed the apiRef OT plugin, apparently. Specializations work and the catalogs were adjusted by the OT Integrator. However, after reading OxygenXML's documentation on transformation scenarios, I could not get around how to create a Transformation scenario that uses my own XSL exte...

Never mind: it was my fault. I was forcing an element defined in a domain specialization in the content model of a topic type specialization's element. Is there a way to produce this effect? I.e., forcing an element defined in a domain specialization in the content model of a topic type specializati...

I'm on the same crossroad and I do not get a Validating Scenario to work. This is what I am doing: 1. I'm editing myFile.dita file with this doctype: <!DOCTYPE restNamespace PUBLIC "-//Intel//DTD DITA REST Namespace Type//EN" "../dtd/restNamespace.dtd"> 2. The restNamespace type ...