Generate Output is failing

[MarcB]

I am on Windows 7 Professional SP 1 and have just upgraded an XMetaL 10.0 installation to version 12. I am testing the installation before asking my team to do the upgrade (40 seats).
The only customization I made in the Advanced Output Configuration was adding the line: “DSDK_PARAM_ditaext = dita” like we had in XMetaL 10.0.

When I attempt to Generate Output for DITA Map or DITA Topic, I get an error. This was working in XMetaL 10.0 fine. This is what I see in the extended log:

[pre]Input file: C:UsersmbeDocumentsfbl_stuffdocumentationSVN_VAsvnsagdocsourcesengeneraltrunkx_global_reusere-product_names.dita
Output file: C:UsersmbeDocumentsfbl_stuffdocumentationSVN_VAsvnsagdocsourcesengeneraltrunkx_global_reusemultiple_html_outre-product_names_new.html
  DITA-OT Path: C:PROGRA~3SoftQuadXMetaLSharedDITA_OT2.4
  Transtype: xhtml
Transformation: Multiple HTML files
Parameters:
  DSDK_PARAM_indexshow = no
  DSDK_PARAM_artlbl = no
  DSDK_PARAM_draft = no
  cmd_default_config_topic = DITA15_1B9FF196523E459683C958FA9E31EEEE;C:PROGRA~2XMETAL~2.0AuthorDITAXACssharedRENDIT~1print_dita20.xml;0C41D0FDB1A24CE9B3FA702F1A85C0C5;C:UsersmbeAppDataRoamingSoftQuadXMetaL12.0print_local.xml; ;C:UsersmbeDocumentsfbl_stuffdocumentationSVN_VAsvnsagdocsourcesengeneraltrunkx_global_reusemultiple_html_outre-product_names_new.html;C:UsersmbeDocumentsfbl_stuffdocumentationSVN_VAsvnsagdocsourcesengeneraltrunkx_global_reusere-product_names.dita;
  DITA_OT_DIR = %XMETAL_SHARED_ALL%DITA_OT2.4
  __DITA_OT_DIR = %XMETAL_SHARED_ALL%DITA_OT2.2
  ANT_PARAM_args.xmfo.java_maxmemory = 1024m
  ANT_OPTS = “-Xmx1024m”
  run_plugin_integrator = no
  cmd_always_open_log = no
  cmd_fs_sandboxing = no
  cmd_cms_sandboxing = yes
  cmd_dita_ot_per_user_version = disable
  _rem_cmd_synchro_mode = 2
  DSDK_PARAM_ditaext = dita
  cmd_open_with = system_default
  DSDK_PARAM_OUTEXT = html
Log path: C:UsersmbeAppDataLocalTempXMetaLrenditionsloglog.txt

  ↓    call ant dita2xhtml -d -Dargs.input=”c:/users/mbe/documents/fbl_stuff/documentation/svn_va/svn/sag/doc/sources/en/general/trunk/x_global_reuse/re-product_names.dita” -Doutput.dir=”C:UsersmbeDocumentsfbl_stuffdocumentationSVN_VAsvnsagdocsourcesengeneraltrunkx_global_reusemultiple_html_out” -Dtranstype=xhtml -Ddita.temp.dir=C:PROGRA~3SoftQuadXMetaLSharedDITA_OT2.4temp -Ddita.dir=C:PROGRA~3SoftQuadXMetaLSharedDITA_OT2.4 -Dgenerate.copy.outer=”3″ -Dargs.xmfo.java_maxmemory=1024m -Dargs.logdir=C:UsersmbeAppDataLocalTempXMetaLRENDIT~1log -Dargs.indexshow=no -Dargs.artlbl=no -Dargs.draft=no -Dargs.filter=C:UsersmbeDOCUME~1FBL_ST~1DOCUME~1SVN_VAsvnsagdocsourcesengeneraltrunkX_GLOB~1MULTIP~1re-product_names.ditaval -Ddita.ext=.dita
  ↓    BUILD FAILED
Errors summary (22):  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  java.lang.NoSuchFieldException: _isNotSecureProcessing
  ↓  Caused by: net.sf.saxon.trans.XPathException: An empty sequence is not allowed as the value of variable $colspec
  ↓  The system cannot find the file specified.
[/pre]

Any ideas?

Thanks,
Marc Beckers
Software AG

Reply

[Derek Read]

This sounds a bit like the issues described here:
https://github.com/dita-ot/dita-ot/issues/2212
https://github.com/dita-ot/dita-ot/issues/1715

I'm not sure what the best resolution will be. If you have a table that has an without @colnum set then I would say adding it might be the easiest solution. Assuming that is the trigger that is the cause for your problem and that it is the same issue. I'm not sure because I can't reproduce the issue.

Or you might try getting XMetaL Author Enterprise 12 to run an older version of the DITA Open Toolkit. But in the tracker above they seem to say that issue affects versions older than 2.2.2, so 2.4 should be OK. If you want to try an older You can do that by changing a parameter in the Other Output Parameters section on the Advanced tab in Tools > Configure Output.

By default XMetaL Author Enterprise 12 is configured to run DITA OT version 2.4 but installs 2.4, 2.2 and 2.0.

To change the version use this parameter:

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%DITA_OT2.4

Or

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%DITA_OT2.2

Or

DITA_OT_DIR  =  %XMETAL_SHARED_ALL%DITA_OT2.0

Reply

[MarcB]

Reverting to
DITA_OT_DIR  =  %XMETAL_SHARED_ALL%DITA_OT2.0
did the trick.
DITA_OT2.2 returned the same error.

Of 3860 elements in the document, 3856 had @colname, which is inserted by XMetaL automatically when you edit tables. XMetaL does not insert @colnum on cells.
I think the problem starts when you merge cells (which I did using the XMetaL 12 GUI). Then @colname disappears, @namest and @nameend take over, and the error occurs.
I have 4 cells that do that, thus making up the number.
This phenomenon is also reported in https://github.com/dita-ot/dita-ot/issues/2212

For the moment, I will direct the team to use DITA_OT2.0 in the Other Output Parameters, but the feeling of unease prevails…..

Thanks, Derek.

Marc Beckers
Software AG

Reply

[Derek Read]

Sounds like a good solution.

Sorry about saying to check for @colnum on entry elements. That is of course not actually allowed in a CALS table. It is the colname as you suggested (and discussed in all of those DITA trackers).

XMetaL Author does get rid of the colname when you merge cells. Most of the time we try to keep the XML to a minimum where possible. Because colname is not needed in this case it is dropped. It seems a bit odd that the DITA OT would be checking for that though. It is not actually a required element at all (according to the DTDs) so I'm not sure what it is even validating against in this case (or if this is validation). A table without any colname values will validate according to the DITA DTDs. It will also render correctly (at least in XMetaL Author) because in this case the order of the entry elements is then assumed to be the order they should appear in the row (left to right) as described in the CALS spec.

Reply

[Author]

Posts