I’m experiencing the following behavior. I set an AS
Number variable to null prior to sending to a remote object. On the backend
(Java), the Number is converted to a 0. The expected data type on the Java end
is a Long (object, not primitive). This is causing us problems since we expect
a null Long object to be represented as null in the database, not 0, and as an
indicator of a new object that needs to be inserted rather than updated. Is this expected behavior/mapping? Is it a bug? I can fix it
on the backend with some additional logic, but I’d rather not have to do
that. Thoughts? Thanks. ------------------------------------------------- Jim Schneider KJ Interactive, Inc. 1-877-370-6906 1-612-605-5399 -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [flexcoders] Flex2: AS Number to Java Long mapping Jim Schneider
- RE: [flexcoders] Flex2: AS Number to Java Long mapping Matt Chotin
- RE: [flexcoders] Flex2: AS Number to Java Long mapp... Jim Schneider