Title:
Bug 77819:The problem I’m having is that component is a restricted keyword in CF script now, so if you have a structure created in CFScript that is passed through a function call and into <cfinvoke> as an attri
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Jon Hartmann / Jon Hartmann (jon.hartmann)
Created: 06/09/2009
Components: Language, CFSCRIPT
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 / 245853
Priority/Frequency: Normal / Unknown
Locale/System: English / Win All
Vote Count: 0
Problem:
The problem I’m having is that component is a restricted keyword in CF script now, so if you have a structure created in CFScript that is passed through a function call and into <cfinvoke> as an attributeCollection, you can’t specify the attribute "component" as part of the collection (as it errors out when you declare it)
In other words, in CF on Wheels, they have a function $invoke() that passes its arguments into a <cfinvoke> tag via the attributesCollection attribute. One of those attributes is "component", however calling
$invoke(component=test, ....);
Fails in cfscript, because component is now a restricted keyword. In the short term I got around this by changing them all to $invoke(comp=test, ...) and then adding handling to set arguments.component = arguments.comp before the cfinvoke, but I’m kind of curious as to how a user is supposed to get around this and/or how the tagless version of invoke works in CFScript.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3038858
External Customer Info:
External Company:
External Customer Name: Jon Hartmann
External Customer Email: 3124041A447C75CA99201549
External Test Config: 06/09/2009Attachments:
Comments: