(prepare for 5000 of the same answer)
You do need both... CFPARAM takes care of if a Fuseaction was not defined,
and the CFDEFAULTCASE catches a fuseaction that does not exist.
Shan
Shannon Hicks
Senior Developer
[EMAIL PROTECTED]
http://www.duodesign.com
duoDesign eBusiness Accelerator
1007 Church Street, Suite 510
Evanston IL 60201
847-491-3211 direct
847-491-3000 main
847-491-3100 fax
-----Original Message-----
From: Stephen Fernandez [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 10:30 AM
To: Fusebox
Subject: RE: Fusebox EBOOK sample chapter online
in the code below (taken from chapter 4 of the new fusebox ebook which is
available online at the www.secretagents.com website)
a <cfparam> for the fuseaction is given, but a <cfdefaultcase> is also
given.
Is there any reason why you would need to do both? surely one or the
other should suffice?
<CFPARAM name="attributes.fuseaction" de fault="hello"> <!--- Basic T
echnique 3 --- >
<CFSWITCH expression="#attributes.fuseaction#">
<CFCASE value="goodbye">
<CFINCLUDE template="dsp_goodbye.cfm">
</CFCASE>
<CFCASE value="hello">
<CFINCLUDE template="dsp_hello.cfm">
</CFCASE>
<CFDEFAULTCASE>
<CFINCLUDE template="dsp_hello.cfm">
</CFDEFAULTCASE>
</CFSWITCH>
_______________________________________
Stephen Fernandez, Web Developer, NetBenefit plc
T: +44 (020) 7336 6777
F: +44 (020) 7336 0567
http://www.netbenefit.com/
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
