tracker issue : CF-3039459

Problem:

CF is not allowing me to 'type' arguments within a cfscript function method signature AFTER the first custom type.  For example;public void function test(required String test, required MyCustomCfc custom, required AnotherCustomCfc another) {}Of course, the correct import statements exist at the top of the file ensuring that the custom types are being included (per the documentation).CF is fine with typing the first custom data type (MyCustomCfc) but simply does not like the types of any subsequent ones.  So the error that is thrown indicates incorrect typing of the argument - which is not true.  The only work around is to type the subsequent arguments as "Any".  Which makes the hair stand up on the back of my neck.Changing the order of the MyCustomCfc and AnotherCustomCfc arguments within the method signature simply causes CF to throw the same error indicating that again, the second custom type is not valid.
Method:

<!--- put this arg.cfm in test/fol1 -->
<cfscript>
import test.*;
public void function test(Base another,Base custom) 
{ 
	writedump(arguments);
}
test( new Child(), new Base()); 
</cfscript>

//child.cfc
component Child extends="Base" {
}

// Base.cfc
component Base {
}

Result:

The SERVICE argument passed to the parseContext function is not of type InjectionService.If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible.

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

Watson Bug ID:	3039459

External Customer Info:
External Company:  
External Customer Name: Brian Carr
External Customer Email: 722B31AC451C344D9920157F
External Test Config: 07/28/2009

Attachments:

Comments: