You're right on track, Andy. So far everything you've stated is
correct. Let me see if I can help you towards the "lightbulb".
The Fusebox process assembles fuses according to a hierarchy
consisting of the application configuration file (fusebox.xml) and
the circuit configuration file (circuit.xml) for the requested
fuseaction. There is only one fusebox.xml per application, while
there is a circuit.xml for each circuit. Fusebox puts things
together in this order:
- Fusebox.xml
- preProcess plugin (if any)
- preFuseaction plugin (if any)
- global preprocess fuseaction (if any)
- Handoff to circuit.xml:
- prefuseaction (if any)
- requested fuseaction
- postfuseaction (if any)
- global postprocess fuseaction (if any)
- postfuseaction plugin (if any)
- postprocess plugin (if any)
(This is taken from p. 230 of my book, "Fusebox 4 & FLiP: Master-
Class ColdFusion Applications".)
If the requested fuseaction uses the <do> verb to call other
fuseactions as part of its job, those requests are processed in the
same way before control returns to the global postprocess fuseaction
in fusebox.xml.
- Jeff
On 15 Feb 2005 at 16:25, Andy Mcshane wrote:
> Hi Jeff, yes I am hoping for the 'lightbulb' effect to kick in real quick! At
> the moment just as I thiunk I am 'getting it' I manage to confuse myself
> again. I am presently stuck on getting my head around the Circuit.xml files
> at the moment. In my fusebox.xml file I have the defaultfuseaction set to
> login.userdetails, I do not have anything entered into my main circuit.xml
> file. I have a circuit called login and inside that i have a circuit.xml
> file with a fuseaction called 'userdetails' that then includes a
login page. My idea being that once I have validated the login I will redirect
to another circuit called default that will also contain a circuit.xml file
that contains a fuseaction called 'homepage' that includes the default homepage
file and holds the page output inside a contentvariable (with me so far?) and
also a 'do' call that builds the page presentation that then refers to the
contentvariable. I think that I am getting tied up on the whole
pre/postfuseaction, globalfuseactions, etc bit. Am I hea
> ding along the right lines with my thinking here? Are you able to have
> pre/post fuseactions inside every circuit.xml file if needed? Am I barking up
> ther wrong tree here? God my head hurts!!!
>
http://www.GrokFusebox.com
"Fusebox 4 & FLiP: Master-Class ColdFusion Applications"
Now available at ProtonArts.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49
Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6605
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/12
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:12
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.12
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
