Errors

Contents

The following sections describe the different types of runtime errors that can occur.

Binding errors occur when a requested component is not found. Binding errors include:

•Object Not Found: No suitable matches are found. (The binding attributes that were provided are wrong.)

•Ambiguity: More than one component matches the binding attributes provided. The attributes need to be modified (by adding or changing rules) so a unique match will be found.

When an Ambiguity error occurs, the Java Log provides information about the different candidates that were found (hierarchy, class, description, etc.).

In the following example, an Ambiguity exception is thrown because 2 radio buttons (with almost identical attributes) match the given binding attributes.

Exception classes:
Jacada.WinFuseNG.Core.BindAmbiguityException
Exception messages:
candidate array has 2 elements.;ClassName=javax.swing.JRadioButton, Name=null, Caption=Radio Three, Index=3, GeneralIndex=5, ToolTip=null, ChildrenCount=0, ParentChildrenCount=5, Parentpath=JPanel.JPanel.JFrame;

ClassName=javax.swing.JRadioButton, Name=null, Caption=Radio Three Index=3, GeneralIndex=4, ToolTip=null, ChildrenCount=0, ParentChildrenCount=5, Parentpath=JPanel.JPanel.JFrame;

The following figure illustrates the position of the radio buttons in the UI (left side) and in the component hierarchy (right side):

In a case like this, it is recommended to add the GeneralIndex attribute to the binding attributes that you provide in the project code.

These types of errors result from listening and send/receive failures.

Error Name	Description/Notes
Port Listening Failure	Failure to listen to the Java application port. The failure log number is written to the log file.
IO Receiving/Sending	Failure to send or receive information, e.g., a command operation.

These types of errors involve failures related to operations and parameters.

Error Name	Description/Notes
Invoke Operation	Failure to invoke a specific operation (e.g, button click, get text, etc.). Detailed information, such as wrong parameters or control is not idle state, is written to the log files.
Wrong Parameters	One or more parameters are wrong, e.g., index is out of bounds.

Serialize Errors

Serialize errors occur when the serialization process in the Java side / C# side fails. Detailed information about the failure reason is written to the log file.