Title:
Bug 78025:I have a remote object call from flex that was set up the following way:
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Todd Sharp / Todd Sharp (cfsilence)
Created: 06/18/2009
Components: Flex/Flash, Flex remoting
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Major / Unknown
Locale/System: English / Win All
Vote Count: 0
Duplicate ID: CF-3038713
Problem:
I have a remote object call from flex that was set up the following way:
<mx:RemoteObject id="svc" endpoint="/flex2gateway/" destination="ColdFusion" source="model.foo">
<mx:method name="xxx" ... />
</mx:RemoteObject>
In actionscript I call it like so:
var params:Object = new Object();
params.one = 'one';
params.two = 'two';
svc.xxx.send(params);
I'm noticing a change in behavior compared to 8 where I'd have been able to address each key of the AS Object as if they were arguments passed to the method - arguments.one, arguments.two, etc -- now though, I notice that if I have declared a cfargument in my method, the AS object is passed as if it were a struct being passed in positionally which is breaking my legacy code.
Should this be considered a bug, or was I simply being dependent on an unintended feature in CF 8?
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3038950
Deployment Phase: Release Candidate
External Customer Info:
External Company:
External Customer Name: Todd Sharp
External Customer Email: 7A924EE2445A4FDB992015D5
External Test Config: 06/18/2009Attachments:
Comments: