CargoReader Class
Properties Methods Events Config Settings Errors
The CargoReader class is optimized for Cargo-IMP documents, providing a simple way to parse Cargo-IMP documents.
Syntax
ipworksedi.Cargoreader
Remarks
The class allows you to parse a Cargo-IMP message. Below are example steps:
- First, use LoadSchema to load a schema file into the class. (Only necessary when preserving document structure).
- Open a Cargo-IMP message or stream by setting input via SetInputStream, InputFile or InputData.
- Call the Parse method to parse the message.
- When parsing is complete, you can retrieve the parsed values from the Values collection.
During parsing, the class performs basic validation of the incoming document. If validation fails, a warning is generated (fired as an event).
Schemas are written in JSON format:
{
"name": "FSU",
"desc": "FSU MESSAGE",
"children": {
"1": {
"desc": "Standard Message Identification",
"children": {
"1.1": {
"desc": "Standard Message Identifier",
"value": "FSU"
},
"1.2": {
"value": "/"
},
"1.3": {
"desc": "Message Type Version Number",
"format": "n[...3]"
},
"1.4": {
"value": "\r\n"
}
}
},
"2": {
...
For example schemas and questions, please contact support@nsoftware.com.
Property List
The following is the full list of the properties of the class with short descriptions. Click on the links for further details.
Errors | A collection of errors that occurred when parsing the Cargo-IMP messages. |
InputData | The data to parse. |
InputFile | The file to parse. |
Values | Collection of values after parsing the Cargo-Imp messages. |
Method List
The following is the full list of the methods of the class with short descriptions. Click on the links for further details.
Config | Sets or retrieves a configuration setting. |
LoadSchema | Loads a schema file describing a Message type. |
Parse | Parse the specified input data. |
Reset | Resets the class. |
SetInputStream | Sets the stream from which the class will read the data to parse. |
Event List
The following is the full list of the events fired by the class with short descriptions. Click on the links for further details.
Error | Fired when information is available about errors during data delivery. |
ResolveSchema | Fires whenever a new Cargo-Imp message is encountered and no schema is found for it. |
Config Settings
The following is a list of config settings for the class with short descriptions. Click on the links for further details.
CloseStreamAfterProcessing | Specifies whether or not the InputStream should be closed after processing. |
BuildInfo | Information about the product's build. |
GUIAvailable | Whether or not a message loop is available for processing events. |
LicenseInfo | Information about the current license. |
MaskSensitive | Whether sensitive data is masked in log messages. |
UseDaemonThreads | Whether threads created by the class are daemon threads. |
UseFIPSCompliantAPI | Tells the class whether or not to use FIPS certified APIs. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
Errors Property (CargoReader Class)
A collection of errors that occurred when parsing the Cargo-IMP messages.
Syntax
public CargoErrorList getErrors();
Remarks
This property is populated with error information. After calling Parse, check this property to determine if any errors occurred while parsing the message. If there are any errors present, the Values collection will likely be incorrect.
This property is read-only and not available at design time.
Please refer to the CargoError type for a complete list of fields.InputData Property (CargoReader Class)
The data to parse.
Syntax
public String getInputData(); public void setInputData(String inputData);
Default Value
""
Remarks
This property specifies the data to be parsed.
Input Properties
The class will determine the source of the input based on which properties are set.
The order in which the input properties are checked is as follows:
- SetInputStream
- InputFile
- InputData
InputFile Property (CargoReader Class)
The file to parse.
Syntax
public String getInputFile(); public void setInputFile(String inputFile);
Default Value
""
Remarks
This property specifies the file to be processed. Set this property to the full or relative path to the file which will be processed.
Input Properties
The class will determine the source of the input based on which properties are set.
The order in which the input properties are checked is as follows:
- SetInputStream
- InputFile
- InputData
This property is not available at design time.
Values Property (CargoReader Class)
Collection of values after parsing the Cargo-Imp messages.
Syntax
public CargoValueList getValues();
Remarks
This property will be populated with the values from the Cargo-IMP message after parsing is complete.
This property is read-only and not available at design time.
Please refer to the CargoValue type for a complete list of fields.Config Method (Cargoreader Class)
Sets or retrieves a configuration setting.
Syntax
public String config(String configurationString);
Remarks
Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
LoadSchema Method (Cargoreader Class)
Loads a schema file describing a Message type.
Syntax
public void loadSchema(String fileName);
Remarks
This method parses the File and loads it into an internal schema list.
If the schema file does not exist or cannot be parsed as an Cargo-IMP schema, the class throws an exception.
Schemas are written in JSON format:
{
"name": "FSU",
"desc": "FSU MESSAGE",
"children": {
"1": {
"desc": "Standard Message Identification",
"children": {
"1.1": {
"desc": "Standard Message Identifier",
"value": "FSU"
},
"1.2": {
"value": "/"
},
"1.3": {
"desc": "Message Type Version Number",
"format": "n[...3]"
},
"1.4": {
"value": "\r\n"
}
}
},
"2": {
...
For example schemas and questions, please contact support@nsoftware.com.
Parse Method (Cargoreader Class)
Parse the specified input data.
Syntax
public void parse();
Remarks
This method parses the input data specified by SetOutputStream, InputFile or InputData.
Input Properties
The class will determine the source of the input based on which properties are set.
The order in which the input properties are checked is as follows:
When a valid source is found the search stops.Reset Method (Cargoreader Class)
Resets the class.
Syntax
public void reset();
Remarks
When called, the class initializes itself to its default state.
SetInputStream Method (Cargoreader Class)
Sets the stream from which the class will read the data to parse.
Syntax
public void setInputStream(java.io.InputStream inputStream);
Remarks
This method sets the stream from which the class will read the data to parse.
Input Properties
The class will determine the source of the input based on which properties are set.
The order in which the input properties are checked is as follows:
When a valid source is found the search stops.Error Event (Cargoreader Class)
Fired when information is available about errors during data delivery.
Syntax
public class DefaultCargoreaderEventListener implements CargoreaderEventListener { ... public void error(CargoreaderErrorEvent e) {} ... } public class CargoreaderErrorEvent { public int errorCode; public String description; }
Remarks
The Error event is fired in case of exceptional conditions during message processing. Normally the class throws an exception.
The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
ResolveSchema Event (Cargoreader Class)
Fires whenever a new Cargo-Imp message is encountered and no schema is found for it.
Syntax
public class DefaultCargoreaderEventListener implements CargoreaderEventListener { ... public void resolveSchema(CargoreaderResolveSchemaEvent e) {} ... } public class CargoreaderResolveSchemaEvent { public String messageIdentifier; public String version; }
Remarks
The ResolveSchema event will fire when a the class encounters a new Cargo-IMP message, but it finds no schema corresponding to it already loaded.
MessageIdentifier contains the message type, such as "FWB" or "FSU".
Version contains the version of the schema used by the message.
When processing this event, the caller can use LoadSchema() to load a new schema into the class that can be used to parse the transaction.
CargoError Type
This type contains the details of an error that occurred while parsing a Cargo-IMP message.
Remarks
The fields below provide information about the error.
Fields
Description
String (read-only)
Default Value: "0"
The description of current error.
Line
int (read-only)
Default Value: 0
The text line where the error occurred.
Offset
int (read-only)
Default Value: 0
The text offset where the error occurred.
Position
int (read-only)
Default Value: 0
The text position where the error occurred.
CargoValue Type
A value parsed from a Cargo-Imp message.
Remarks
The fields below provide information about the value.
Fields
Description
String (read-only)
Default Value: "0"
The description of current value.
Level
int (read-only)
Default Value: 0
The level of the value within the message. The elements in the message are grouped by levels where: Level 1 is the Text Element Level Level 2 is the Data Group Level Level 3 is the Data Element Level Each element is allocated a numeric reference within the Cargo-IMP Message. For example, a ULD Description might be: 4. ULD Description Level 1 4.1 Total Number of ULDs Level 2 4.2 ULD Identification Level 2 4.2.1 ULD Type Level 3 4.2.2 ULD Serial Number Level 3 4.2.3 ULD Owner Code Level 3 4.3 ULD Position Restriction Indicator Level 2 4.4 Weight of ULD Level 2 4.4.1 Weight Code Level 3 4.4.2 Weight Level 3
Line
int (read-only)
Default Value: 0
The text line of the current value.
Name
String (read-only)
Default Value: "0"
The name of the element. This will be a string like "1", "1.2", or "1.2.2", and is defined in the schema file.
Offset
int (read-only)
Default Value: 0
The text offset of the current value.
Position
int (read-only)
Default Value: 0
The text position of the current value.
Value
String (read-only)
Default Value: "0"
The value of the element.
Config Settings (Cargoreader Class)
The class accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.CARGOREADER Config Settings
Base Config Settings
In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the class does not attempt to process external events.
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these classes: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
The Java edition requires installation of the FIPS certified Bouncy Castle library regardless of the target operating system. This can be downloaded from https://www.bouncycastle.org/fips-java/. Only the "Provider" library is needed. The jar file should then be installed in a JRE search path.
In the application where the component will be used the following classes must be imported:
import java.security.Security;
import org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider;
The Bouncy Castle provider must be added as a valid provider and must also be configured to operate in FIPS mode:
System.setProperty("org.bouncycastle.fips.approved_only","true");
Security.addProvider(new BouncyCastleFipsProvider());
When UseFIPSCompliantAPI is true, SSL enabled classes can optionally be configured to use the TLS Bouncy Castle library. When SSLProvider is set to sslpAutomatic (default) or sslpInternal an internal TLS implementation is used, but all cryptographic operations are offloaded to the BCFIPS provider in order to achieve FIPS compliant operation. If SSLProvider is set to sslpPlatform the Bouncy Castle JSSE will be used in place of the internal TLS implementation.
To enable the use of the Bouncy Castle JSSE take the following steps in addition to the steps above. Both the Bouncy Castle FIPS provider and the Bouncy Castle JSSE must be configured to use the Bouncy Castle TLS library in FIPS mode. Obtain the Bouncy Castle TLS library from https://www.bouncycastle.org/fips-java/. The jar file should then be installed in a JRE search path.
In the application where the component will be used the following classes must be imported:
import java.security.Security;
import org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider;
//required to use BCJSSE when SSLProvider is set to sslpPlatform
import org.bouncycastle.jsse.provider.BouncyCastleJsseProvider;
The Bouncy Castle provider must be added as a valid provider and must also be configured to operate in FIPS mode:
System.setProperty("org.bouncycastle.fips.approved_only","true");
Security.addProvider(new BouncyCastleFipsProvider());
//required to use BCJSSE when SSLProvider is set to sslpPlatform
Security.addProvider(new BouncyCastleJsseProvider("fips:BCFIPS"));
//optional - configure logging level of BCJSSE
Logger.getLogger("org.bouncycastle.jsse").setLevel(java.util.logging.Level.OFF);
//configure the class to use BCJSSE
component.setSSLProvider(1); //platform
component.config("UseFIPSCompliantAPI=true");
Note: TLS 1.3 support requires the Bouncy Castle TLS library version 1.0.14 or later.
FIPS mode can be enabled by setting the UseFIPSCompliantAPI configuration setting to true. This is a static setting which applies to all instances of all classes of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.
For more details please see the FIPS 140-2 Compliance article.
Note: Enabling FIPS-compliance requires a special license; please contact sales@nsoftware.com for details.
Setting this configuration setting to true tells the class to use the internal implementation instead of using the system security libraries.
This setting is set to false by default on all platforms.
Trappable Errors (Cargoreader Class)
CargoReader Errors
1000 Invalid schema file. | |
1001 No schema found. | |
1002 Schema format error. | |
1003 Line or message was too long. | |
1004 Failed to parse the message version. | |
1005 Element is not in the schema file or is not a simple element. | |
1006 Could not find the element. |