Doesn't that defeat the purpose? What if I want to plug child
into another application, where the alias "ch1" is already
taken?
> -----Original Message-----
> From: Bob Silverberg [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 3:52 PM
> To: Fusebox
> Subject: RE: Nesting circuits: I just don't get it! :(
>
>
> I'm not up on "official" XFB, but I believe the flaw in what you've said
> below is that you would _never_ call
> /grandparent/parent/index.cfm?fuseaction=child.doChildStuff. You always
> call /grandparent/index.cfm?fuseaction=circuit.fuseaction - so it doesn't
> matter where you are or what you're calling. You always call the root
> fusebox and then it figures out where to go (i.e., which circuit(s) in
> include) to find the proper fuseaction.
>
> N'est pas?
>
> Bob
>
> -----Original Message-----
> From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
> Sent: March 28, 2001 3:19 PM
> To: Fusebox
> Subject: Nesting circuits: I just don't get it! :(
>
>
> I just can't get the light bulb to come on when it comes
> to nesting circuits.
>
> Here's what I understand: A circuit may have "child"
> circuits that it uses to do specific tasks. These
> children are stored in subdirectories instead of
> just pointing to the fuseaction, we point to the
> circuit name and the fuseaction, using that dot
> notation.
>
> That all makes sense. What I don't get is how a
> self-contained circuit can become the child of
> another circuit. How does it refer to its own
> methods?
>
> For example, suppose my app looks like this (I'm
> using -'s to represent circuits and +'s to represent
> fuseactions
>
> - grandparent
> + doGrandParentStuff
> + doSomething
> - parent
> + doParentStuff
> - child
> + doChildStuff
> + doSomething
> - otherparent
> - child
> + doChildStuff
> + doSomething
>
> Suppose parent is my home circuit. I have an XFA
> that tells child to "doSomething" after it finishes
> with "doChildStuff." This works fine when child
> is the home circuit. I just call
> /grandparent/parent/index.cfm?fuseaction=child.doChildStuff
> and it redirects to
> /grandparent/parent/index.cfm?fuseaction=child.doSomething
>
> But what if I want grandparent to be the home app? I know
> I can register parent.child in the circuits.cfm and call
> it something like "ch1." That will allow me to use
> /grandparent/index.cfm?ch1.doChildStuff, but when
> doChildStuff exits to doSomething, it will blow up
> because /grandparent/index.cfm?child.doSomething is
> invalid.
>
> How do I get around that? Am I doing something wrong?
>
> Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
