HI David,

first off, you will probably do better directing your question to the FB
lists at  [EMAIL PROTECTED]  , which is dedicated to fusebox topics
generally

Second, you want your controller to manage the requests to the Model and the
View, so your controller might look like

<fuseaction name="welcome">
    <do action="" />
    <do action="" />
</fuseaction>

with your Model looking like
<fuseaction name="getData">
    <include template="dsp_getData.cfm" />
</fuseaction>

and similarly in the View

you'll notice that I dropped the "qry" and "dsp" nomenclature on the
fuseactions in the controller since those are used just as conveniences in
naming *fuses*, not fuseactions. Your fuseactions can have whatever name you
want, though a good practice might be to begin with a predicate

----- Original Message -----
From: "David Adams" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 4:02 PM
Subject: Do Fuseactions in the controller need to be linked?

> I am learning FBX4 using a MVC design approach.  I have a question on
whether or not each of the fuseactions in the controller's circuit.xml.cfm
file have to be linked to each other.
>
> My problem arises when I have a series of fuseactions and only the first
one fires. For example in the following example only the 'welcome'
fuseaction fires and nothing else.
>
> <circuit access="public">
> <fuseaction name="welcome">
> <do action=""> > </fuseaction>
> <fuseaction name="querydatabase">
> <do action=""> > </fuseaction>
> <fuseaction name="displaydata">
> <do action=""> > </fuseaction>
> </circuit>
>
> Do I have to provide a link from one fuseaction to the next, as shown
below?  Help or comment would be appreciated.
>
> <circuit access="public">
> <fuseaction name="welcome">
> <do action=""> > <do action=""> > </fuseaction>
> <fuseaction name="querydatabase">
> <do action=""> > <do action=""> > </fuseaction>
> <fuseaction name="displaydata">
> <do action=""> > </fuseaction>
> </circuit>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to