Ronan, the reason they aren't being passed out is that ONE of the XFAs
passed in (the value of one, I should say) will be the fuseaction passed
out. See if this sample code makes it clearer:
--> XFA.submitForm: a FUSEACTION
<form action="self" method="post">
<input type="hidden" name="fuseaction"
value="#attributes.XFA.submitForm#">
....
Hal Helms
== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ==
-----Original Message-----
From: Ronan O'Donohoe [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 14, 2001 3:54 PM
To: Fusebox
Subject: RE: Question: Why the change from RFA to XFA method?
>From studying the SimpleContactManager I see the XFA being passed into the
included template. In any of those templates the fusedocs don't show that
one or any of the XFA will be passed out. Shouldn't they be?
I expected to see this...
|| Atributes ||
--> XFA.continue: Fuseaction
<-- [XFA.continue]: Fuseaction
or even this if there is one the one XFA possible.
|| Atributes ||
<-> XFA.continue: : Fuseaction
Ronan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
