Chapter 18. Common problems

18.1. <oXygen/> opens a XML document after a long time. Why does it happen?
18.2. My file was created with other application and and it contains special characters like é, ©, ®, etc. Why does <oXygen/> display a square for these characters?
18.3. When I run a transformation in the XSLT Debugger perspective it is very slow. Can I increase the speed?
18.4. When I start <oXygen/> on Windows XP I get the following error. What can I do? Cannot start <oXygen/>. Due to:java.lang.NullPointerException java.lang.NullPointerException at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source) at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source) at com.sun.java.swing.plaf.windows.XPStyle.getDimension(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsProgressBarUI.getPreferredInnerHorizontal(Unknown Source)
18.5. <oXygen/> crashed the JVM, what happened?
18.6. When I do a keyword search in the User Manual the search highlights the wrong word in the text, often several words after the keyword. Is this a bug?
18.7. Why can't I access a remote file by HTTP in <oXygen/> while in Internet Explorer it works just fine? I am sure my proxy settings are correct.
18.8. My Java Input Method does not work in <oXygen/> on my Linux computer. I installed it in the [JRE-home-folder]/lib/ext folder but the activation shortcut does not work in <oXygen/>. What can I do?
18.9. How do I set the version X of the Java virtual machine for <oXygen/> on Mac OS X?
18.10. On my Mac OS X machine when I double-click on the <oXygen/> icon the application doesn't start / gives a Segmentation fault error.
18.11. After upgrading my OS X version to 10.4.x / my <oXygen/> version to 6.x <oXygen/> is not associated to the file types XML, XSL, XSD, etc. This worked in the previous version of <oXygen/>.
18.12. After upgrading my Mac OS X to version 10.4.1 Tiger I am not able to set all XML files to open with <oXygen/> when I click Change All in the Get Info dialog. This worked in OS X 10.3.x.
  18.1.

<oXygen/> opens a XML document after a long time. Why does it happen?

All the content of your document is on a single line or the document is very large. If the content is on a single line please enable the Format and indent the document on open preference from OptionsPreferences+Editor / Format / XML before opening the document. If the document is very large (above 10 MB) you should increase the memory available to <oXygen/>.

  18.2.

My file was created with other application and and it contains special characters like é, ©, ®, etc. Why does <oXygen/> display a square for these characters?

You must set a font able to render the special characters from Font preferences. If it is a text file you must set also the encoding used for non XML files. If a TrueType font installed on the computer is not accessible in the Font preferences the Java virtual machine is not able to load the system fonts. It is a problem of the Java virtual machine and a possible solution is to copy the files of the font in the [JVM-home-folder]/lib/fonts folder.

  18.3.

When I run a transformation in the XSLT Debugger perspective it is very slow. Can I increase the speed?

Disable rendering of output to the XHTML Output view during the transformation process if the transformation produces HTML or XHTML output. In order to view the output result run the transformation in the Editor perspective with the option "Open in browser" or run it in the Debugger perspective, save the Text output area to a file and use an external browser for viewing.

  18.4.

When I start <oXygen/> on Windows XP I get the following error. What can I do?

    Cannot start <oXygen/>.
    Due to:java.lang.NullPointerException
    java.lang.NullPointerException
    at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source)
    at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source)
    at com.sun.java.swing.plaf.windows.XPStyle.getDimension(Unknown Source)
    at com.sun.java.swing.plaf.windows.WindowsProgressBarUI.getPreferredInnerHorizontal(Unknown Source)
                        

The error is cause by a a bug in the Java runtime from Sun Microsystems. You can avoid it by setting the Java system property com.oxygenxml.no.xp.theme to the value true in the startup script. If you start <oXygen/> with the oxygen.bat script just add the parameter

-Dcom.oxygenxml.no.xp.theme=true

to the java command in the script. If you start <oXygen/> from the Start menu shortcut add the same parameter to the line Virtual Machine Parameters in the file [oXygen-install-folder]\oxygen.ini.

  18.5.

<oXygen/> crashed the JVM, what happened?

Java applications can't do this. The problem is a bug in the JVM. Depending of your platform, there is information logged about what caused the crash. For Unix type systems you will get an error in the console (and for Mac OS X you may also get a report in ~/Library/Logs/CrashReporter/JavaApplicationStub.crash.log). Some problems with Java 1.4.x and Windows were the result of a bug in the JVM and certain graphics card drivers.

  18.6.

When I do a keyword search in the User Manual the search highlights the wrong word in the text, often several words after the keyword. Is this a bug?

You get wrong highlights only when <oXygen/> runs with a Java 1.4 virtual machine. The search highlights are correct when <oXygen/> runs with a Java 1.5 virtual machine. It is a problem of the JavaHelp indexer supplied by Sun Microsystems. In order to see correct highlights you have to use Java 1.5.

  18.7.

Why can't I access a remote file by HTTP in <oXygen/> while in Internet Explorer it works just fine? I am sure my proxy settings are correct.

If the same proxy settings work in Internet Explorer but not in <oXygen/> probably the proxy server or the HTTP server which hosts the remote file requires NTLM authentication. The <oXygen/> HTTP client does not support this type of authentication. You should set as proxy in <oXygen/> a proxy server capable of using standard HTTP credentials (basic authentication, digest authentication) to authenticate with a NTLM server.

  18.8.

My Java Input Method does not work in <oXygen/> on my Linux computer. I installed it in the [JRE-home-folder]/lib/ext folder but the activation shortcut does not work in <oXygen/>. What can I do?

You have to remove the xml-apis.jar file from the [oXygen-install-folder]/lib folder and run <oXygen/> with a Java 1.5 virtual machine or with a Java 1.6 one. With a Java 1.4.2 virtual machine Java Input Methods do not work in <oXygen/> on Linux computers due to a conflict between some classes included in the core Java classes and other classes with the same class name and package name included in oXygen and on which oXygen depends. oXygen does not work correctly if it is forced to use the core Java version of these classes. Starting with Java 1.5.0 the classes were moved to other package.

  18.9.

How do I set the version X of the Java virtual machine for <oXygen/> on Mac OS X?

<oXygen/> uses the first JVM from the list of preferred JVM versions set on your Mac computer that has the version number not less than 1.4.0. You can move your desired JVM version up in the preferred list by dragging it with the mouse on a higher position in the list of JVMs available from Applications -> Utilities -> Java -> Java Preferences.

  18.10.

On my Mac OS X machine when I double-click on the <oXygen/> icon the application doesn't start / gives a Segmentation fault error.

Install the latest Java update from the Apple website. If that doesn't solve the problem copy the file JavaApplicationStub from the /System/Frameworks folder to the oxygen.app/Contents/MacOS folder. For browsing the folder oxygen.app Meta + click on the <oXygen/> icon and select Show Package Contents

  18.11.

After upgrading my OS X version to 10.4.x / my <oXygen/> version to 6.x <oXygen/> is not associated to the file types XML, XSL, XSD, etc. This worked in the previous version of <oXygen/>.

The upgrade damaged the file associations registry on your Mac OS X machine. Please rebuild the registry with the following procedure. This will reset all file associations and will rescan the entire file system searching for applications that declare file associations and collecting them in a database used by Finder.

 

Procedure 18.1. Rebuild file associations registry

  1. Find all the <oXygen/> installations on your hard drive.

  2. Delete them by dragging them to the Trash.

  3. Clear the Trash.

  4. Unarchive the installation kit on your desktop.

  5. Copy the contents of the archive into the folder /Applications/Oxygen.

  6. Run the command

    /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user -dump

    from the Terminal.

  7. Restart Finder with

    killall Finder

    from the Terminal.

  8. Create a XML or XSD file on your desktop. It should take the <oXygen/> icon.

  9. Double click it. After accepting the confirmation dialog <oXygen/> will be start up.

  18.12.

After upgrading my Mac OS X to version 10.4.1 Tiger I am not able to set all XML files to open with <oXygen/> when I click Change All in the Get Info dialog. This worked in OS X 10.3.x.

On Mac OS X Tiger you must add an entry to the Info.plist file. Tiger was released after <oXygen/> version 6.0 so we could not include the change in the release. Please close <oXygen/>, press Meta + click on the <oXygen/> icon, select Show package contents, go to Contents, edit the Info.plist file, add the entry

    <key>CFBundleIdentifier</key>
    <string>ro.sync.exml.Oxygen</string>

and restart <oXygen/>. Select Change All in the Get Info dialog to make the association.