Known problems

Problems which are solved by upgrading XXE and/or the Java^TM runtime are not listed here. Therefore, the first thing to do if you have problems is to upgrade XXE to latest version and to upgrade Java^TM to latest supported version (no beta please!).

See also Frequently Asked Questions.

Known problems on Windows 

Known problems on the Mac

Known problems on Linux

Known Java^TM Web Start problems

Known problems when XMLmind XML Editor runs as an applet

Known problems on Windows

• On Windows 7, some icons (Up One Level, Home, Create New Folder, etc) are missing at the top/right of the file chooser dialog box.

  Workaround: None. This is a known Java^TM bug (Bug ID: 2183124). It should be fixed by forthcoming Java^TM runtime 1.6.0_18.

• Xxe.exe fails to find any installed 64-bit Java^TM runtime.

  Workaround: upgrade to XXE v4.4+.

• When XXE is started in a directory which has an UNC filename (example: \\home\jsmith), opening documents is very slow or fails with strange error messages such as "Cannot open file XXX: www.oasis-open.org".

  Workaround: when XXE is started in a directory which has an UNC filename, loading the XML catalog XXE_install_dir/addon/config/catalog.xml silently fails. Therefore, the workaround is to start XXE in a directory which has not an UNC filename, for example: C:\.

  In order to do this:

  1. Right-click on the XMLmind XML Editor ``icon'' that you use to start XXE. For example, right-click on the XMLmind XML Editor menu item found in the Start menu > All Programs > XMLmind XML Editor menu.
  2. This will display a popup menu. Then select the Properties menu item.
  3. This will display a dialog box. Then select the Shortcut Tab and change the Start in field to, for example, "C:\".
  4. After that, always start XXE using this modified ``icon''.

Known problems on the Mac

• Input methods do not work inside the document view.

  Workaround: upgrade to XXE v4.4+ and turn on option "Use integrated input method support" (Options|Preferences, Edit section).

• Printing large documents consumes an enormous amount of memory and can cause XXE (i.e. the Java^TM VM) to crash with a bus error.

  No workaround.

• Dragging the icon which looks like a bookmark in the node path bar does not work.

  No workaround.

• As of Java^TM 1.5.0_07 running on Mac OS X 10.4.9, the popup list displayed by the auto-completion feature of the Tools|Execute dialog box is blank. Auto-completion of command names and command parameters works, but the list containing the suggestions is not properly rendered. (Clicking on the resize corner of the dialog box makes it appear, but this cannot be seriously considered to be a workaround.)

  Workaround: upgrade to Mac OS X 10.5 (Leopard).

Known problems on Linux

• When KDE 4's Klipper is running, Edit|Copy (Ctrl-C) and the X selection behave strangely, which make XXE almost unusable.

  Workaround: Make sure that the "Prevent empty clipboard" checkbox is not checked (Configure Klipper, General Config). Also use a Java^TM 1.6 runtime rather than a Java^TM 1.5 runtime.

• XXE randomly hangs for a couple of minutes. This seems to only happen on Linux with a Java^TM runtime 1.6+.

  Workaround: using an external application, update the contents of the clipboard by copying a small piece of text.

• When using window managers such as fvwm2, the XXE main window is displayed at a wrong place with a wrong size.

  Workaround: Java^TM seems to be tested only against the Gnome and KDE standard window managers. Therefore, you unfortunately need to use another window manager.

Known Java^TM Web Start problems

• Deployment of XMLmind XML Editor using Java^TM Web Start does not work with Java^TM 1.5.0_16 due to Java^TM bug #6746185.

  Workaround: Use a version of Java^TM other than 1.5.0_16 on the machine running XMLmind XML Editor.

• Using both the -indexjars and -packjars options for deploywebstart allows to deploy a working applet, but not a working Java^TM Web Start application. When both options are used, XMLmind XML Editor deployed using Java^TM Web Start does not start and reports false missing class errors.

  No workaround.

Known problems when XMLmind XML Editor runs as an applet

• The applet fails to start. This often happens after upgrading the Web browser and/or the Java^TM runtime.

  Possible workaround: first make sure that your Web browser really runs the next generation Java plug-in and not the legacy Java plug-in. (More information in Deploying XXE as an applet, Requirements.)

  If this is already the case, please redeploy the applet by running deploywebstart, but this time using the latest JDK and without any of the following options: -jsapplet, -indexjars, -packjars. (More information in The deploywebstart command-line tool.) However doing this does not always fix the problem, which often lies in the Web browser and/or in the Java plug-in itself.

• When deploywebstart has been used with the -indexjars option, trying to convert a document to PDF using Apache FOP will raise an obscure ClassCastException.

  Workaround: Do not use the -indexjars option if you need to run FOP from within the applet.

• When a DITA topic or map is opened in the applet, a cryptic error message is displayed if you attempt to use any of the Convert Document menu items. This problem is caused by the way the DITA Open Toolkit has been integrated in XMLmind XML Editor.

  Workaround: upgrade to XXE v4.5+. Starting from this version, XMLmind DITA Converter replaces the DITA Open Toolkit when it comes to converting DITA documents to other formats.

• Using the File menu to reopen a recently opened document found on an HTTP server requiring the user to authenticate himself will cause the applet to hang.

  Workaround: Use the -auth command-line option (wrapped in applet parameters) to pass the applet authentication credentials for that HTTP server.

• On Windows, a 32-bit Web browser will fail to find any installed 64-bit Java^TM runtime. In such case, the applet will suggest to download and install a 32-bit Java^TM runtime.

  Workaround: Use the 64-bit version of the Web browser.

• Firefox 3 on Windows only. Minor applet repaint bugs.

  No workaround.

• Firefox 3 on Linux only. Opening a dialog box which is part of the applet (e.g. the "Find Element" dialog box) and then closing it will fail to return the keyboard focus to the applet.

  No workaround.

• Firefox 3 on Linux only. The applet may steal the keyboard focus from the form fields displayed in the same HTML page as the applet.

  No workaround.

• Firefox 3 on Linux only. Applet scripting randomly hangs for 30 seconds or so.

  No workaround.