tracker issue : CF-3335540

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

[ANeff] ER for: add invoke()'s argument array support to cfinvoke

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 09/23/2012

Components: Language

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final / 286508, 288858

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 0

invoke() accepts an arguments array. cfinvoke does not. Could cfinvoke also accept an arguments array?


1) Use this code (defines an array and a function):

  argsArray = [1,'one',2,'two','','three'];
  function myFunction() {return listToArray(arrayToList(ARGUMENTS),",",true);}

2) Run this code (passes array to function via invoke()):

<cfset writeDump(invoke("", "myFunction", argsArray)) />

2) See result: [1,'one',2,'two','','three'] (good!)
3) Run this code (passes array to function via cfinvoke)

<cfinvoke method="myFunction" returnvariable="foo" argumentCollection="#argsArray#" />

4) See result: "coldfusion.runtime.Array cannot be cast to java.util.Map" (not so good)

First, thanks very much for adding argument array support to invoke(). Can this argument array support also be added to cfinvoke?

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3335540

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:



Could this be extended to simply allow arrays of ordered args in any place argumentCollection is used? ie: not simply for <cfinvoke> ? That's be really cool! -- Adam
Comment by External U.
17996 | September 05, 2013 09:36:42 AM GMT
We should not be fixing this so late in the release cycle. Will take this up later.
Comment by Awdhesh K.
17997 | March 03, 2014 01:44:56 AM GMT
You know you've had this on your plate for over a year, right? Almost a year and a half. What you shouldn't be doing is *leaving it until so late in the cycle to look at things*. You need to get a decent triage system in place. This attitude you have of "close everything every release, and we'll look at it next release" clearly doesn't work, and is borderline farce. -- Adam
Comment by External U.
17998 | March 03, 2014 02:36:17 AM GMT
Huh? So now it's fixed? Is that right? -- Adam
Comment by External U.
17999 | March 03, 2014 10:50:25 AM GMT