This has been resolved in the upcoming version of FB.
A workaround could be to replace the Error in the wsdl with a different word and use the WSDL to generate appropriate classes.
After this you could use the convertResultHandler property (by pointing to your custom function) in the WebService class to actually convert the result to appropriate classes.
By default FB uses a result handler function convertResultHandler defined in com.adobe.serializers.utility.TypeUtility in serializers.swc
Hope this helps.
Is this fixed in the Burrito preview?
About convertResultHandler, I defined it as such:
<mx:WebService id="reportingServices" convertResultHandler="WebServiceTest.convertResultHandler" ...>
public static function convertResultHandler(result:*, operation:AbstractOperation):*
But response is caught by the fault handler with "faultCode:DecodingError". Is there a way to define a response handler higher up in the flow for parsing the response? (It's a multipart/related response)
You might want to look at your database field names and make sure you're not using names that match Actionscripts reserved name types. There's possibly an illegal name in your database field list.
In my case, I had a field called 'classes' in my database that produced the same error. When I changed it to 'myClass' the error was resolved.
I'm not sure if this is useful.