You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@flex.apache.org by AAE <al...@yahoo.com> on 2019/03/01 00:54:21 UTC

Need 0 instead of NULL in BlazeDS 4.7.3

We are in the process of upgrading to BlazeDS 4.7.3 from 3.2 to take
advantage of the Deserialization security benefits. 

Our legacy app was built around the NaN being sent as 0 limitation.
Unfortunately the fact that NaN is now coming across the wire as NULL will
cause issues. 

Is there a configuration option to revert to version 3.2 behavior?

Thanks in advance



--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/