Found something interesting today in the course of trying to solve a problem in my sample LCDS application:
Why are my ValueObject member variables undefined in the results from my RemoteObject requests?
The Flash Player deserializes objects in a special order that can confuse developers used to object serialization from other RPC systems. When a strongly typed object is returned to the player it first creates an instance from the prototype of the registered class without calling the constructor. It then populates the object with the properties sent in the result and finally, it calls the constructor without arguments. If your ValueObject constructor expects arguments to initialize an instance be sure to check whether arguments were actually sent to the constructor before overriding member variable values. Note that the Flash Player does not currently honor getter/setter properties in object serialization or deserialization.
I have been dealing with this exact problem – an object referenced (Product) by the objects returned from my data service (LineItem) are not typed, but are instead only of type Object. This was not an easy problem to track down because it did manifest itself as I would have expected. Will post an update with a solution when I find one.
I ran into this problem again while testing a new application that we are building and I found a "fix" of sorts. If the class is referenced somewhere in the Flex application (instead of just including it), the class will be compiled into the application. Once compiled, the Flash player will deserialize the object to a strongly typed object instead of a weak one (e.g. of type "Product" instead of "Object").
This is not the most of elegant solutions, so please comment with better options. I hope the Flex team takes a look at this problem soon.