tracker issue : CF-4199848

select a category, or use search below
(searches all categories and all time range)

ColdFusion 11, Update 12 breaks Flex remoting in some cases (not fixed in Update 13)

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/Workaround

Reporter/Name(from Bugbase): Peter Legg / Peter Legg ()

Created: 09/29/2017

Components: Flex/Flash, Flex remoting

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: 11,0,12,302575 and 11,0,13,303668 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Linux

Vote Count: 2

Problem Description: Installation of Update 12 (required for IAVA) results in the Flex error in the attached file.  Expected functionality has been confirmed when uninstalling updates back to Update 10 (went from 10 to 12).

Steps to Reproduce: NA

Actual Result:See attachment

Expected Result: Display of table data

Any Workarounds: None


  1. September 29, 2017 00:00:00: CF 11 Update 12 - Flex error.docx


Discussion of issue at
Comment by Peter L.
281 | September 29, 2017 01:26:10 PM GMT
Please add the following snippet in the services-config.xml file in WEB-INF\flex directory and restart the server. <validators> <validator class="flex.messaging.validators.ClassDeserializationValidator"> <properties> <allow-classes> <class name=""/> </allow-classes> </properties> </validator> </validators> It worked for customer. We have to validate, if we should add the validator tag by default, hence marking it to ToFix/Validate.
Comment by HariKrishna K.
29487 | December 12, 2017 05:00:45 AM GMT
Update 13 still has this issue, as noted. The issue only seems to occur if you pass an ArrayCollection from Flex to a function in a .CFC file on the ColdFusion server. If you pass in an array of strings, for example, it doesn't happen. If you pass in a complex object that is pre-defined in a CFC file ( a "value object") this issue doesn't occur. If you stringify your ArrayCollection (via a JSON Serializer, which can be obtained from a 3rd party, found with a simple Google search) this issue will not occur. Your receiving function in your .CFC file will need to be changed, of course, to accept a string instead of an array. You can de-stringify it once you've got the data in your .CFC's function.
Comment by Laurence M.
282 | January 18, 2018 05:54:17 PM GMT
Tracker is not letting me vote for this. "You can't vote for a bug you created." I didn't create this bug report. WTF? UPDATE: It finally allowed me to vote for it. :)
Vote by Jack D.
283 | January 18, 2018 08:42:04 PM GMT
It'd be nice if Adobe fixed this bug, but see my comment for a possible work-around.
Vote by Laurence M.
284 | January 18, 2018 09:55:06 PM GMT