We have a pretty big application with lots of objects being passed between flex and java. One object in particular has a subtle bug:
It's a plain old java object being passed to the flex front end (using blazeds producer/consumer messaging). The POJO has two String properties such as:
myShirt.color = "brown";
myShirt.description = "winter shirt with 3 buttons";
when I get the object on the frontend, in Flex, the value object's properties are swapped, as in:
myShirt.color = "winter shirt with 3 buttons";
myShirt.description = "brown";
Clearly, this is some type of confusion blazeds is having when the objects are serialized/deserialized. Since they are both Strings, it seems something is getting confused when reading/writing the objects.
Both objects exactly mirror each other with parameters and methods in the same order in the files with the same names.
How do I correct the serialization, preferably without having to handle it on my own?
Thanks in advance for any suggestions.