Hi B,
No the circuit aliases have no impact on your CFINCLUDE or CFMODULE locations.  These must still reference relative or mapped locations.  In your example, you would probably do this:
<cfinclude template="#fusebox.rootpath#Administration/Rules/actValidateEmail.cfm">

The circuit aliases are only used in the double-barrelled "circuit.fuseaction".  In other words, the circuit alias is part of the description of a particular high-level function of a Fusebox application.

As an alternative to reusing the low-level actValidateEmail.cfm fuse, you could expose the email validation as a high-level, public fuseACTION.  If you did that, then you could reuse that function via CFMODULE:
<cfmodule template="#fusebox.rootpath#index.cfm" fuseaction="adminrules.ValidateEmail" address="#emailaddress#">

So you have a few options.

Hope that help,

Best of luck
LeeBB

----- Original Message -----

 

If I wrote some code that, for example, vaidates an email address and
wanted to reuse it, how do I include it in a fuseaction? I'm confused
the fbx_circuits file provides the aliases to the folders.  Do I need to
use absolute URLs to refernece other fuses?  i.e., if my file
actValidateEmail.cfm was in the Rules (see below) folder, do I use:

<cfinclude template="/myApp/Administration/Rules/actValidateEmail.cfm">

or does the cicuit mapping also provide aliases for template location??


Thanks in advance!

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to