LCDs can only communicate with the J2EE server. Currently, only the data type and data type conversion of ActionScript 3.0 are asymmetrical.
Data Type correspondence during actionscript3.0 conversion:
ActionScript data type ----------------- Java Data Type
Null ------------------- null
Number ------------------- java. Lang. Number
Boolean ------------------- java. Lang. Number, Boolean, java. Lang. String
String ------------------- java. Lang. String, java. Lang. Boolean, Boolean, java. Lang. character, Char, java. Lang. Number
Date ------------------- java. util. Date
XML Object ------------------- org. W3C. Dom. Document
When Java converts data types to ActionScript 3.0
Java data type ----------------- actionscript3.0 Data Type
Null ------------------- null
Java. Lang. Number ----------------- number
Java. Lang. Number, Boolean ------------------- Boolean
Java. Lang. String, java. Lang. Character char [] ----------------- string
Java. util. Collection, java. Lang. Reflect. array ----------------- Array
Java. util. Map, java. util. dictionary ----------------- object
Org. W3C. Dom. Document ------------------- XML Object
Class ------------------- object
List, arraylist ----------------- arraycollection
In the process of calling Java code using LCDs, data type conversion occurs directly without explicit calling.
For example, if an arraylist is returned through Java, the arraylist contains hashmaps. if you call this method using remoteobject (or other methods), the flex side must receive an object, which can be forcibly converted to arraycollection. then, the arraycollection is traversed to obtain the object storing each data (hashmap in Java ). there is no map class in flex, but the map key in Java can be accessed as an attribute of the object.