One simple solution is that in each index.cfm for any circuit (sub-circuit)
is to climb "backward" through the directory structure via app_locals.cfm
(each app_locals in every circuit first calls its parent app_locals). The
"final" app_locals is in the home application root directory and it calls
all the necessary setup routines to get these variables set.
Using the XFB model, that is technically switched when the circuit it not an
application circuit. In otherwords, you always start at the home
application's index.cfm which calls other files (I usually repeat with an
app_locals just to be consistent) to set up these variables, then the nested
process cascades down a directory tree to the final circuit and fuseaction.
Does that help or only confuse more?
-----Original Message-----
From: Shawn Regan [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 04, 2001 11:07 AM
To: Fusebox
Subject: Request Scope in XFB
Hey guys,
I was wondering, do I need to set the request.cfroot and request. etc..
again in each fuse curcit's app_locals.cfm? I can't seem to get my curcits
to pickup this unless I set them again for each curcit. Am I missing
something? I have the Fusebox book and have read some of it but not in great
detail. I know fusebox I have been coding in this style for a year now. But
this is my first application done in the XFB model.
Shawn Regan
Applications Developer
Pacific Technology Solutions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
