You're right on track, Amir. Your fuseactions would become two-part dotted
notation, just as you suggest with "objects.somefuseaction". Index.cfm in your
homeapp directory would become the top-level or master fusebox file; all
actions would call that file, which would in turn include the circuit fusebox
specified by the first half of your fuseaction.
- Jeff
On 27 Mar 2001, at 4:32, Amir Razmjou wrote:
> Hi to all Fuseboxers.
> I faced a problem that doesn�t sound to be problem but I just want to know
> what do you do in this case. I saw fusebox archive but I didn't find related
> message.
> I have two nested circuit application in my home application something
> like
>
> homeapp/admin/objects
>
> I have some defined XFAs in my "objects" application using dot-notation,
> some of them is sent to other circuit applications like "usr.newUsr", and so
> many of them will be send back to the first application they came from
> (�objects� app). Like "admin.objects.newObject" and so forth. The problem is
> that while it's obvious that I want the "admin.objects.newObject" to be
> sending as local I have to type "admin.objects.somefuseaction" each time I'm
> defining a local XFA.
> So What if I wanted "objects app to not be admin's child and I wanted to
> make it child of root home application like this
>
> homeapp/admin
> homeapp/objects
>
> I should change all XFAs from "admin.objects.somefuseaction" to
> "objects.somefuseaction"? Isn't this against "encapsulation" concept that
> fusebox follows?
> Is there something that I got wrong about fusebox?
>
> Related code:
> ---------------------------------------------------------
> <!--- FILE: //fuseboxapp/admin/objects/index.cfm --->
>
> <cf_translateAndPrepareFuseactionSomehow>
>
> <cfswitch expression="#attributes.fuseaction#">
> <cfcase value="home">
> <cfset attributes.XFA.onFailed = "admin.objects.failed">
> <cfset attributes.XFA.onSuccess = "admin.objects.success">
> <cfset attributes.XFA.onNewObject = "admin.objects.newObject">
> <cfset attributes.XFA.onDelete = "admin.objects.deleteObject">
> <cfinclude template="dsp_objects.cfm>
> </cfcase>
> <!--- and so forth --->
> </cfswitch>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
