I have seen errors like this when I have a Flex/as3 side class with that looks like this
public var wheels:Array;
Then if the service returns a car instance that is typed as an ArrayCollection then it will choke. I would try narrowing it down the to the service that is returning the conversion error and using something like Charles to see what is being returned by the service.
Well the properties I am using are explicitly set to Array as my BlazeDS config is set to use Array instead of ArrayCollection (legacy-collection = true). If I remove my Class (in your example Car) from my Project entriely, then Flex defaults to using Object. In the instances returned by BlazeDS and deserialized using the Object-Class, I can see that my "wheels" property is correctly set to Array and not ArrayCollection. So this cannot be the issue.
My question is: How can I debug this error? Is there a way I can somehow set a Breakpoint or just get a Stack-Trace of the place where the error is comming from?
Have you narrowed it down to the service call and object class that is the subject of the error. ?
Well as I mentioned:
If I remove all of my model class definitions from my project and hereby force Flex to use Object there shouldn't be any TypeError. If I set a breakpoint in my server side class, I get the errors in my console as soon as I continue to send back the result (So it is related to the data sent back from the server). As I have only one callback registered for this call and the Error appears before the callback function is actually called, the error has to be outside of my code. But as I mentioned ... how can I get a stacktrace at where it's comming from?
I don't know if you are going to get a line number as is customary with other errors. I think the deserialization is ocurring deep within the bowels of the flashplayer, out of reach for us mere mortals.