Page tree
Skip to end of metadata
Go to start of metadata

This article details common error messages displayed while initializing EditLive! for Java Swing. For each type of error message, this article details how to locate the source of the error and how to solve the problem.

XML Configuration File Error Messages 

These errors will cause the Java application to display the following error message where the instance of EditLive! for Java Swing should be located:

An error occured while initializing. Please see Java console for details.

There are two different basic conditions. If the following pop-up dialog appears, the error indicates an incorrect path to the EditLive! for Java Swing configuration file was specified:

Error 3: Failed to load YOURCONFIG.xml

where YOURCONFIG.xml is the name of the EditLive! for Java Swing configuration you've specified.

If no pop-up dialog accompanies the error then there is a syntax error in the EditLive! for Java Swing configuration file. This is usually due to a syntax error entered by a developer manually editing the configuration file.

Character Encoding Error Message

This error message will be shown by the following display in EditLive! for Java Swing:

The required encoding for this document, XXXencodingMethodXXX, is unavailable on this system.

where XXXencodingMethodXXX represents the encoding method specified.

This error message reflects a problem with the character encoding method used for the content in EditLive! for Java Swing. Fixing this error will require locating where the character encoding was specified and specifying an acceptable character encoding method. The Specifying Character Sets in the Swing SDK article details the three methods used to specify character encoding for EditLive! for Java Swing and its supported character sets.

Licensing Error Messages

These messages will be displayed in a separate pop-up window from the EditLive! editor. Licensing information is specified in an EditLive! configuration file. For information on how to specify an EditLive! licence, see the <license> Configuration File Element article and the Licensing EditLive! article.

Common errors include:

Account Not Found Error

This error will be shown by the following message in a pop-up window:

Licence error 203: Account not found

This error refers to an incorrect value being place in the key attribute of a <license> configuration file element. Make sure the product key provided by Ephox is correctly entered into this attribute.

License Domain Error

This error will be shown by the following message in a pop-up window:

Attempting to use an unlicensed domain

This error refers to an incorrect value being placed in the domain attribute of a <license> configuration file element. Make sure the organization's domain registered with Ephox is correctly entered into this attribute (commonly, the domain displayed by browsers in an organization is the domain name registered with Ephox).

NoClassDefFound Error

Upon compiling you may encounter the following error message in the Java console:

Exception in thread "main" java.lang.NoClassDefFoundError: com/ephox/editlive/ELJBean

This error indicates that the required EditLive! for Java Swing files weren't correctly added to the classpath.

  • No labels