<cfparam name="url.method">

<!--- This function is placed in the "variables" scope. --->
<cffunction name="hello" output="false">
      <cfreturn "hollow ddorld">
</cffunction>

<cfset result = "">
<cfif structKeyExists(variables,url.method)>
      <cfinvoke method="#url.method#" returnvariable="result">
</cfif>

 <!--- Clear any previously generated output and output the result. --->
<cfsetting showdebugoutput="false">
<cfcontent reset="true"><cfoutput>#result#</cfoutput><cfabort>

<cfparam name="url.method">
<cftry>
<cfinvoke method="#url.method#" returnvariable="foo"></cfinvoke>
<cfcontent reset="true">

<cfoutput>#foo#</cfoutput>
<cfcatch></cfcatch>
</cftry>

<cffunction name="hello">
<cfreturn "hollow ddorld">

</cffunction>

No need to hate CF, bad work man and all that

First off, i agree the wddx wrapper is a pain, although back in the day i used to write loads of stuff utilizing wddx, but there are many ways around it. A cfm file like you suggest is one, but lets find a better way than evaluate() \shudder\

how about this..

#foo#

personally i’d prefer to expose my model by creating a remote proxy that wraps my model methods, and if you specify returntype=”xml” on your remote methods cf won’t wrap them in a wddx packet

Now, if you were on CF8 (i know not everyone is..) you could use the returnFormat=json argument and hey presto