Having the exact same issue going form CF8 to CF9. Runs flawlessly on CF8, yet on CF9 I get that exact same error.
1 person found this helpful
In CF9, we have introduced some changes in Flash remoting. Because of that there are few changes in WEB-INF/flex.Config-XML files at Destination and Channel level. Some of the Elements which used to exist at Channel level in CF8/CF7, have now been shifted to Destination level in CF9.
I would suggest you to go through this "Enhanced Flash Remoting" feature doc to get idea about changes done. By Default CF9, now ships XML files with these new changes. And a Recompilation of your Old Flex Application is required to be done against these new Config XML files.
I dont know, how you have migrated your Channels/Destinations from CF7 to CF9. Migration changes are mentioned in the Doc. Please go through it.
If you can answer some of these questions, I will have better clarity.
--> Do you Observe any Error related to Flash remoting on Server startup?
--> Have you directly copied your OLD CF7 Config-XML files on CF9?
If YES, this means that Old Flash remoting is being used on CF9 and so You dont need to Recompile your Flex Application and it should just work fine the way it used to work in CF7/CF8.
If NO, it means that you are using "Enchanced/Improved Flash Remoting" feature of CF9 But with Flex Application compiled with CF7/CF8 Style Flash Remoting. In this case, refer to the Documentation and add your Required Destinations as per the new Flash remoting specification.
CF9 continues to support CF7/CF8 style Flash Remoting as well and whether to use OLD Flash Remoting or New Flash remoting will be decided by CF based upon the Format of the Config XML files.
--> Are these Flex Application using LCDS as well?
In our case, the issue turned out to be that the new AMF de-serializer does not understand per-app settings, in this case mappings.
We had some mappings in the application.cfc used by our service. Those mappings were not working when executing the value objects.
The fix was to put the mappings in the CF Administrator, but that really should be made into a bug.
Thanks, Jayesh, we'll try that! Sorry, I didn't realize there was a whole upgrade path for Flex apps and CF9.
Ok...so CF7 to CF9 migration problem may not be because of AMF de-serializer not entertaining PerApp Mapping settings as PerApp setting feature was introduced in CF8 only. Where as CF8 to CF9, if somebody has perApp mapping settings, then it seems to be broken.
I have the exact same problem even when compiling using the CF9 config files.
Compilation in FB, shouldnt fail because of Config XMl changes. Could you tell me what is the compilation error that you are getting ?
BTW, On CF server side, what remoting you are using OLD remoting(cf8/cf7 style) or NEW (cf9) one?
Do you see any Messagebroker related Errors on Server startup?