The chapter on Data Serialization in the BlazeDS Developer Guide has
tables that show, for example, an AS Number deserializes to
java.lang.Double, and a Java double passed to AS is converted to a
Number, but that seems to be wrong. In fact the conversions seem to
be based on the values, not the types.
For example, if I send Number(268435455) to Java, it comes through as
java.lang.Integer. If I add one (268,435,456), then it comes through
as a Double. Similarly, if I send 268435455D ("D" for double literal)
to AS, it comes through as an int. If I add one, it comes through as
a Number.
It so happens that the value 268,435,455 (0xFFFFFFF) is
flex.messaging.io.amf.Amf3Types.INT28_MAX_VALUE
I'm not saying that the behavior is unreasonable, but it seems to
drastically vary from the documentation, if my test code is correct.
I'm testing with ActionScript and Java routines with all parameters
and variables declared as being of type Object, BTW.
