Available data types

You can specify the following data types for the POJO fields and the Bean property.

Table 18-3 Available data types for the POJO fields and the Bean property (JSON to POJO mapping)

No.	Data
1	Primitive	int
2		short
3		long
4		float
5		double
6		char
7		byte
8		boolean
9	Wrapper class	Integer
10		Short
11		Long
12		Float
13		Double
14		Character
15		Byte
16		Boolean
17	java.lang.String
18	java.math.BigInteger
19	java.math.BigDecimal
20	java.util.Date
21	java.util.Calendar
22	java.lang.Enum
23	POJO^#1
24	java.util.List<T>^#2
25	java.util.Set<T>^#2
26	java.util.Map<K,V>^#2
27	Any arrayin 1 through 26^#2,#3

#1: You can recursively have the POJO as a field or a Bean property. For conditions of a supported POJO, see 18.3 JSON to POJO mapping.

#2: The type of T, K, and V can be any item listed in No.1 through 26 in the above table.

#3: The value of the corresponding JSON format must conform to the array structure.

Points to note when setting elements:

If the JSON format has any of the following errors, the JsonParseException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.
- If the JSON format contains a value other than a numeric value, character string, array, object, true, false, or null
- If two objects are not separated with a comma
- If a character that is not allowed is used among tokens (spaces, linefeeds, carriage returns, and horizontal tabs are allowed)
- If the format of a numeric value is incorrect (such as 12, 1.2eE8, 0X3F7A)
If the data type is not a numerical field (1-5, 7, 9-13, 15 of the table) or the JSON format value corresponding to the Bean property is not a numerical value, the JsonMappingException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.

(1) int type(primitive)

(2) short type (primitive)

(3) long type (primitive)

(4) float type (primitive)

(5) double type (primitive)

(6) char type (primitive)

(7) byte type (primitive)

(8) boolean type (primitive)

(9) Integer type (wrapper class)

(10) Short type (wrapper class)

(11) Long type (wrapper class)

(12) Float type (wrapper class)

(13) Double type (wrapper class)

(14) Character type (wrapper class)

(15) Byte type (wrapper class)

(16) Boolean type (wrapper class)

(17) java.lang.String type

If the value of the corresponding JSON format is a blank character string expression, a blank character string expression is mapped.
If the value of the corresponding JSON format is null, null is mapped.
The program must be designed in such a way that quotation marks ("), if any, in the value of the corresponding JSON format must escape. If the quotation marks do not escape, the JsonParseException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.
The program must be designed in such a way that control characters such as \n,\r,\t,and \b, if any, in the value of the corresponding JSON format must escape. If the control characters do not escape, the JsonParseException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.
The program must be designed in such a way that the control character \u in the value of the corresponding JSON format, if existing, must escape. Furthermore, a character string or a hexadecimal value must follow this \u. If the above conditions are not met, the JsonParseException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.

(18) java.math.BigInteger type, java.math.BigDecimal type

(19) java.util.Datetype, java.util.Calendar type

If the value of the corresponding JSON format is null or a blank character string expression, null is mapped.

The standard supported formats are as follows:

yyyy-MM-dd'T'HH:mm:ss.SSSZ
yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
EEE, dd MMM yyyy HH:mm:ss zzz
yyyy-MM-dd

The following table lists pattern characters, describes their meaning, and gives an example wherever applicable:

Element	Meaning	Example
yyyy	Represents years with a four-digit number.	2013
MM	Represents months with a two-digit number.	04
MMM	Represents months with a string of three characters.	Apr
dd	Represents dates of month with a two-digit number.	30
EEE	Represents days of a week with a string of three characters.	Sun
'T'	Is a fixed character.	--
HH	Represents hours of a day with a two-digit number.	23
mm	Represents minutes with a two-digit number.	30
ss	Represents seconds with a two-digit number.	10
SSS	Represents milliseconds with a three-digit number.	978
'Z'	Is a fixed character.	--
Z	Represents a time zone defined in RFC 822.	-0530
zzz	Represents standard time.	IST

Legend:: --: No example is available for fixed characters.

For details on patterns of the Date or Calendar formats, especially E and M depending on the locale, see the information related to the SimpleDateFormat class in the Java SE specifications.

If the value of the corresponding JSON format has an unsupported format, the JsonMappingException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.
If the value of the corresponding JSON format is a number within the range of the long type, i.e. if the value corresponding to the Date or Calendar type is expressed in milliseconds, the objects of the Date or Calendar type initialized with their respective values in milliseconds are mapped. If the value is outside the range of the long type, the operation is not guaranteed.
For example, if the value of the corresponding JSON format is 1346850421185, the result (Date object) of calling the Date(long date) constructor of the Date class by specifying 1346850421185 in the date parameter is mapped to a field or a Bean property of the Date type. Similarly, if you create a Date object, specify that Date object in date parameter and call the setTime(Date date) method of the Calendar class, the result (Calendar object) is mapped to the field or the Bean property of the Calendar type.

(20) java.lang.Enum type

(21) java.util.List<T> type

If the value of the corresponding JSON format is an empty list ([]), an empty list is mapped.
If the value of the corresponding JSON format is null, null is mapped.
If the list of the corresponding JSON format contains null, null is set to the corresponding element in the field of the List<T> type or the Bean property to be mapped.
The value included in the list of the corresponding JSON format must conform to the conditions of the type set to T. For conditions, see notes for the respective types in 18.3.2 Available data types. These notes also describe the operations carried out if the conditions are not fulfilled.

(22) java.util.Set<T> type

If the value of the corresponding JSON format is an empty list ([]), an empty set is mapped.
If the value of the corresponding JSON format is null, null is mapped.
If the list of the corresponding JSON format contains null, null is set to the corresponding element in the field of the Set<T> type or the Bean property type to be mapped.
The value included in the corresponding JSON format set must conform to the conditions of the type set to T. For conditions, see notes for the respective types in 18.3.2 Available data types. These notes also describe the operations carried out if the conditions are not fulfilled.

(23) java.util.Map<K,V> type

If the value of the corresponding JSON format is a blank map ({}), an empty map is mapped.
If the value of the corresponding JSON format is null, null is mapped.
If the map of the corresponding JSON format includes null as a key, the JsonParseException exception is thrown. For details on exception handling, see 18.3.3 Exception handling.
If the map of the corresponding JSON format includes null as the value, null is set to the corresponding values of the fields of the Map<K,V> type to be mapped or in the Bean property.
For a key or a value to be included in the map of the corresponding JSON format, the key or the value must conform to the conditions of the type to be set to K, V respectively. For conditions, see notes for the respective types in 18.3.2 Available data types. These notes describe the operations carried out if the conditions are not fulfilled.

18.3.2 Available data types