I would recommend explicitly passing arguments into a CFC method (or even
a custom tag or UDF ) for various reasons, mainly code reusability. To
pass values into a CFC method, you can use either cfinvokeargument or list
them individually in the cfinvoke tag (just like sending variables into a
custom tag). The cfargument tag is used to define arguments to a function,
not pass the arguments in.
But, onwards to your question, the attributes scope only exists in custom
tags.
In a normal ColdFusion template, if you do this:
<cfset arguments.MyArgument = "value">
You are actually not creating a variable in the arguments scope, since
the arguments scope does not exist. You are creating a structure named
arguments in the local scope (variables). That structure has a single key,
MyArgument.
In CF5, I suspect that this behavior would create a variable named
"arguments.MyArgument" in the local scope because CF5 supports periods in
variable names. CFMX sees the period and automatically creates a structure.
At 08:27 AM 7/16/2002 -0400, you wrote:
>Is the attribute scope available to CFCs?
>I am getting an error that says my form fields are not available to CFCs
>via the attribute scope (im using FB3, thus the attribute scope and not
>form scope).
>
>Ideas? Should I explicitly pass them in using the cfargument tag?
>
>Michael Tangorre
>
>MillenniuM Information Systems
>1101 Wilson Blvd, Suite 1200
>Arlington, Virginia 22209
>(703) 341-1438
>
>================================
>This email contains MillenniuM Information
>Systems, LLC. privileged information.
>================================
>
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
