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 and How To.

Known problems on Windows

• 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 Mac

• 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 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.