The complex event processing language can handle the same data types as Java character strings and primitive data types. Data type descriptions in the complex event processing language are not case-sensitive.
Data type | Explanation | Method for expressing constants (literals) |
|---|---|---|
string | Character string | Enclose with double quotation marks (") or single quotation marks ('). If you want to include double quotation marks (") or single quotation marks (') in a character string, you can use either the method in which the backslash symbol (in a Japanese language environment, the Yen symbol) is placed before a double quotation mark or single quotation mark, or the Unicode method (double quotation mark is \u0022, and single quotation mark is \u0027). |
char/character | Character | There is no constant (literal) expression indicating a single character. |
bool/boolean | Boolean value | true or false |
byte | 8-bit signed integer | Express using 0x followed by 2 hexadecimal characters. |
short | 16-bit signed integer | There is no constant (literal) expression indicating 16-bit signed integers. |
int/integer | 32-bit signed integer | Enter the integer value as is. |
long | 64-bit signed integer | Add L or l after the integer value. |
float | 32-bit float | Add F or f after the numeric value. |
double | 64-bit double precision float | Enter as is a numeric value, including the decimal point or the exponent portion (specify using E or e), or add D or d at the end. |
The event properties entered to Complex Event Processing are converted to the complex event processing language data types shown below in accordance with the data types of the elements defined at "xmlSchema" element in the "event type definition".
XML schema standard primitive data type, derived data type | Complex event processing language data type | |
|---|---|---|
Primitive data type | string | string |
boolean | bool | |
decimal | double (If fractionDigit is specified as 0 in the derived data type: int) | |
float | float | |
double | double | |
duration, dateTime, time, date, gYearMonth, gYear, gMonthDay, gDay, gMonth, hexBinary, base64Binary, anyURI, QName, NOTATION | string | |
Derived data type | string derived data type (normalizedString, token, language, NMTOKEN, NMTOKENS, Name, NCName, ID, IDREF, IDREFS, ENTITY, ENTITIES) | string |
integer, nonPositiveInteger, negativeInteger, nonNegativeInteger, positiveInteger | int | |
long, unsignedLong | long | |
int, unsignedInt | int | |
short, unsignedShort | short | |
byte, unsignedByte | byte | |
Note
Even if the integer type is derived from the decimal type and the long type is derived from the integer type in the XML schema data types, the decimal and integer types both correspond to the int type (the effective number of digits is less than for the long type) in the corresponding complex event processing language data type. Therefore, if long values are used, do not use the integer or decimal type in XML schema.
In addition to true and false, 1 and 0 are permitted as XML schema Boolean values. In the complex event processing language, only true and false can be used as bool (Boolean) values, so do not use 1 and 0 as Boolean values.
