This section contains further explanation about exceptions, warnings and errors originating from the CSO Gateway. Messages associated with exceptions, warnings and errors starts with an identifier that categorize them (see the 2 tables on the right).

Exceptions thrown by the CSO Gateway are instances of ca.metaobjects.csogateway..::.CsoGatewayException. They represent expected problems caused by errors from the user.

Warnings exists to inform the user of something that is not necessarily a problem but deserves attention.

Errors thrown by the CSO Gateway are instances of ca.metaobjects.csogateway..::.CsoGatewayError. They reprensent unexpected situations that may not be solvable by the user.

This topic contains the following sections.

Prefix Kind of message
EXC Exception
WAR Warning
ERR Error
Second prefix Component Example
IImporterEXC-I-022
LLoaderWAR-L-078
NTLNative Type LibraryERR-NTL-003
OGObject GatewayEXC-OG-014
TMType MorpherERR-TM-027

Exceptions in the Importer component

This section contains further explanation about exceptions thrown from the Importer component.

This section contains the following subsections.

EXC-I-000: Request made to this HTTP handler must have exactly one key/value pair in the query string.

The ImporterHttpHandler takes exactly one key/value pair. The key is a command and the value parameters for this command. Most URL for requests made to this HTTP handler are composed programmatically by the Importer control. If you get this exception, you might have composed a malformed URL that goes to this HTTP handler.

EXC-I-001: No command or command unknown. Valid commands are {0}.

Most URL for requests made to this HTTP handler are composed programmatically by the Importer control. If you get this exception, you might have composed a URL with an non-existing command.

EXC-I-002: Circular reference detected among scripts to be imported.

Exceptions in the Loader component

Exceptions in the Object Gateway component

This section contains further explanation about exceptions thrown from the Object Gateway component.

This section contains the following subsections.

EXC-OG-000: The System.Int64 value {0} cannot be precisely represented by a javascript Number value.

This exception will occur when the ExceptionOnPrecisionLossInt64 configuration parameter is true and a value outside the range supported by the javascript data type Number passes in the Object Gateway. See the Configuration topic for more detail.

The only quick workaround to this is to put the config parameter to false and accept some loss in the precision of the value.

EXC-OG-001: The System.UInt64 value {0} cannot be precisely represented by a javascript Number value.

This exception will occur when the ExceptionOnPrecisionLossUInt64 configuration parameter is true and a value outside the range supported by the javascript data type Number passes in the Object Gateway. See the Configuration topic for more detail.

The only quick workaround to this is to put the config parameter to false and accept some loss in the precision of the value.

EXC-OG-002: The System.Decimal value {0} cannot be precisely representation by a javascript Number value.

This exception will occur when the ExceptionOnPrecisionLossDecimal configuration parameter is true and a value with a number of active precision bits greater that what is supported by the javascript data type Number passes in the Object Gateway. See the Configuration topic for more detail.

The only quick workaround to this is to put the config parameter to false and accept some loss in the precision of the value.

EXC-OG-003: Attempt to pass object ({0}) in the CsoGateway failed. The type of this object ({1}) is not cso-compatible.

While recusively going through the object composition graph of the object given to a ObjectGateway control, the Object Gateway has encountered an object that is not already cso-compatible and is not cso-ready either.

This problem can be fixed by finding a way to make the type of the object cso-compatible. If it is a user-defined type, maybe it can be made cso-ready. If it is a type from the .NET Framework, there is nothing that can be done for this version of the CSO Gateway.

Future versions of the CSO Gateway will allow you defined you own cso-types and make the Object Gateway use them to convert a specific type of objects.

Exceptions in the Type Morpher component