TOPIC DESCRIPTION: (provided by the speaker)

We will introduce CI (continuous integration) concepts and benefits. Hopefully you have seen presentations over ant, setting up Jenkins, unit testing and refactoring your code. I always walk away thinking this is awesome but it can be a daunting process to get everything working in one step. This presentation will walk you through a bridge, an intermediate step, you can use immediately in your projects to get usable feedback from Jenkins on your cfml code.

MEETING URL: http://experts.acrobat.com/cfmeetup/

DURATION: Approx. 1 hour

RECORDING: All meetings are recorded. The URL will be posted after meeting at recordings.coldfusionmeetup.com

SPEAKER: (provided by the speaker)

I have worked with ColdFusion since 1999 for several companies. I am an advocate of Eclipse, Source Control, Mylyn, and anything to make developing ColdFusion more productive and easier. My main focus currently is learning Git, Ruby on Rails, and ColdFusion on Wheels. I am an Adobe Community Professional. I have spoken at several user groups and enjoy talking to people about ColdFusion.

WHEN: Thurs. Feb 2, 6:00pm US ET (UTC/GMT-5)

What time is that for you? The following link shows [ what the time would be for you ]. Here’s [ another option ] that shows the time as US ET, and lets you choose your city from the list offered to see what time that is in your own timezone.

DOWNLOADABLE RECORDINGS:

In addition to the streaming recording posted immediately after the meeting (link provided above), we now also post recordings at[ Vimeo ] usually within a day of the meeting.

LOGGING IN: When you login to the Connect room (the experts.acrobat.com/cfmeetup link above) to view the meeting, PLEASE USE THE “LOGIN AS GUEST” option, and USE YOUR NAME, but do NOT attempt to use your meetup.com username/password or any Connect account. Just sign in as a guest.

RSVP, but only if coming: We do appreciate folks RSVPing if they plan to come (using the link on this email or at the meetup site), though it’s not mandatory and it’s not a commitment. But there’s no need to RSVP if you can’t make it let alone explain why you can’t. With over 2,600 members, no worries.

FEEDBACK/MEETING DISCUSSION: Members will receive an email after the meeting or can click a link on the event page to offer. Note also the meeting-specific discussion area there at the bottom, in addition to the one-chance feedback feature on the right. Feel free to engage in discussions about the meeting topic.

ADD THIS TO YOUR CALENDAR: Want to add this event to your own personal calendar? After logging in here , you’ll see an option at the top of the event page, just below the event title,  saying, “Export”, which offers calendar downloads for Outlook, iCal, Google, and Yahoo calendars. (Note that the calendar entry created will show the event taking 2 hours. That’s a default that meetup.com has chosen, which I can’t change. The meetings are generally about an hour, though often go as much as 30-45 minutes longer with Q&A and chat.)

TOPIC DESCRIPTION: (provided by the speaker)

Have you ever wondered what event gateways are and what they can do for you? If so this session is for you. We will cover how you can use event gateways to execute code asynchronously as well respond to and handle real time events. Practical uses like an online auction, a fantasy football draft, processing file uploads in the background, and others will be discussed.

MEETING URL: http://experts.acrobat.com/cfmeetup/

DURATION: Approx. 1 hour

RECORDING: All meetings are recorded. The URL will be posted after meeting at recordings.coldfusionmeetup.com

SPEAKER: (provided by the speaker)

Kurt has been working with ColdFusion since version 4.5. By day Kurt works for the American Academy of Neurology and by night he consults on web  applications for small to medium size businesses. In his spare tech time, he is a member of the Mach II open source project. He recently started a open source project called, AppBooster, which aims to show best practices for using several different frameworks with ColdFusion.

WHEN: Thurs. Jan 26, 6:00pm US ET (UTC/GMT-5)

What time is that for you? The following link shows [ what the time would be for you ]. Here’s [ another option ] that shows the time as US ET, and lets you choose your city from the list offered to see what time that is in your own timezone.

DOWNLOADABLE RECORDINGS:

In addition to the streaming recording posted immediately after the meeting (link provided above), we now also post recordings at[ Vimeo ] usually within a day of the meeting.

LOGGING IN: When you login to the Connect room (the experts.acrobat.com/cfmeetup link above) to view the meeting, PLEASE USE THE “LOGIN AS GUEST” option, and USE YOUR NAME, but do NOT attempt to use your meetup.com username/password or any Connect account. Just sign in as a guest.

RSVP, but only if coming: We do appreciate folks RSVPing if they plan to come (using the link on this email or at the meetup site), though it’s not mandatory and it’s not a commitment. But there’s no need to RSVP if you can’t make it let alone explain why you can’t. With over 2,600 members, no worries.

FEEDBACK/MEETING DISCUSSION: Members will receive an email after the meeting or can click a link on the event page to offer. Note also the meeting-specific discussion area there at the bottom, in addition to the one-chance feedback feature on the right. Feel free to engage in discussions about the meeting topic.

ADD THIS TO YOUR CALENDAR: Want to add this event to your own personal calendar? After logging in here , you’ll see an option at the top of the event page, just below the event title,  saying, “Export”, which offers calendar downloads for Outlook, iCal, Google, and Yahoo calendars. (Note that the calendar entry created will show the event taking 2 hours. That’s a default that meetup.com has chosen, which I can’t change. The meetings are generally about an hour, though often go as much as 30-45 minutes longer with Q&A and chat.)

TOPIC DESCRIPTION: (provided by the speaker)

Lack of integration is a problem in any IDE (Integrated Development Environment). Lack of integration and visibility cause problems within your organization. Point to point integration like ticket systems are errors prone and costly like your ticket system. After this session you will better understand this problem and see how to increase communication and awareness all within your Eclipse based editor like ColdFusion Builder.

MEETING URL: http://experts.acrobat.com/cfmeetup/

DURATION: Approx. 1 hour

RECORDING: All meetings are recorded. The URL will be posted after meeting at recordings.coldfusionmeetup.com

SPEAKER: (provided by the speaker)

I have worked with ColdFusion since 1999 for several companies. I am an advocate of Eclipse, Source Control, Mylyn, and anything to make developing ColdFusion more productive and easier. My main focus currently is learning Git, Ruby on Rails, and ColdFusion on Wheels. I am an Adobe Community Professional. I have spoken at several user groups and enjoy talking to people about ColdFusion.

WHEN: Thurs. Jan 12, 6:00pm US ET (UTC/GMT-5)

What time is that for you? The following link shows [ what the time would be for you ]. Here’s [ another option ] that shows the time as US ET, and lets you choose your city from the list offered to see what time that is in your own timezone.

DOWNLOADABLE RECORDINGS:

In addition to the streaming recording posted immediately after the meeting (link provided above), we now also post recordings at[ Vimeo ] usually within a day of the meeting.

LOGGING IN: When you login to the Connect room (the experts.acrobat.com/cfmeetup link above) to view the meeting, PLEASE USE THE “LOGIN AS GUEST” option, and USE YOUR NAME, but do NOT attempt to use your meetup.com username/password or any Connect account. Just sign in as a guest.

RSVP, but only if coming: We do appreciate folks RSVPing if they plan to come (using the link on this email or at the meetup site), though it’s not mandatory and it’s not a commitment. But there’s no need to RSVP if you can’t make it let alone explain why you can’t. With over 2,600 members, no worries.

FEEDBACK/MEETING DISCUSSION: Members will receive an email after the meeting or can click a link on the event page to offer. Note also the meeting-specific discussion area there at the bottom, in addition to the one-chance feedback feature on the right. Feel free to engage in discussions about the meeting topic.

ADD THIS TO YOUR CALENDAR: Want to add this event to your own personal calendar? After logging in here , you’ll see an option at the top of the event page, just below the event title,  saying, “Export”, which offers calendar downloads for Outlook, iCal, Google, and Yahoo calendars. (Note that the calendar entry created will show the event taking 2 hours. That’s a default that meetup.com has chosen, which I can’t change. The meetings are generally about an hour, though often go as much as 30-45 minutes longer with Q&A and chat.)

Here is the link to the conference: http://opencfsummit.org/

If you missed the part 1 of this tutorial, you may get it here.
Now that we have set up the main Fusebox structure for our application, let’s continue to implement it.

Layouts

Figure 2.1

I want you to pay particular attention to the circuit “layout”. That circuit will not be called by any page, it is an internal circuit, basically a “view” circuit which will assemble all the contents of the page into the layout templates we choose.

Now that we have our “Hello World” page working, let’s play a little with layouts. Suppose you want to have a header, content and footer as your layout (Figure 2.1). First you will have to create the contents for the header, main content and footer blocks and then insert them into the layout template. Let’s see how it is done.
On the fusebox.xml.cfm template there is a tag <globalfuseactions>, followed by two tags <preprocess> and <postprocess>. Every action that you include between those tags will be processed either before or after Fusebox assembles the page.

We will set the header, footer and the layout actions into the <postprocess> tag, because they will be shown at the end of all Fusebox processing.
The code is:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

<globalfuseactions>
<preprocess>
</preprocess>
<postprocess>
<fuseaction action="vhome.header" contentvariable="content.header" />
<fuseaction action="vhome.footer" contentvariable="content.footer" />
<fuseaction action="layout.checkLayout" />
</postProcess>
</globalfuseaction>

Note, in the <postprocess> block, the attribute “contentvariable” in the fuseaction tag. That means Fusebox will process that action and will place the results into a variable instead of rendering it to the screen. Later on, we will use that variable in the layout context. We are calling actions from the “view” of the home circuit. That’s why we are calling the fuseactions vhome.header and vhome.footer before the layout.checklayout, because we want to load the header and footer into variables that will be used in the layout template.

So, let’s work now on the “layout” circuit and prepare the header, footer and default layout templates.

Create a ColdFusion template named dspHeader.cfm and another dspFooter.cfm inside the “home view” folder: \circuits\home\vhome. Add the following code to the templates:

dspHeader.cfm

1
2
3
4
5
6
7

<cfoutput>
<h2>#request.pageTitle#</h2>
<hr/>
</cfoutput>

dspFooter.cfm

1
2
3

<hr/>
<h4>©2009 Your Name</h4>

Now, let’s edit the circuit.xml.cfm template in the “vhome” circuit:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

<!DOCTYPE circuit>
<? xml version="1.0" encoding="UTF-8"?>
<!-- vhome -->
<circuit access="internal" xmlns:cf="cf/">
<fuseaction name="main">
<set name=”request.pageTitle” value=”Fusebox Tutorial” overwrite=”true” />
<include template="dspMain" required="true" />
</fuseaction>
<fuseaction name="header">
<include template="dspHeader" required="true" />
</fuseaction>
<fuseaction name="footer">
<include template="dspFooter" required="true" />
</fuseaction>
</circuit>

With that, we accomplished the Header and Footer to be included in our layout. Notice the setting of the variable request.pageTitle with an attribute of overwrite=’true’; that will be used in the header when included into the layout template. Now, let’s look at the layout itself.

You noticed the call to the layout fuseaction in the fusebox.xml.cfm under the tag <postprocess> in the global fuseactions section:

1
2
3
4
5

<postprocess>
<fuseaction action="layout.checkLayout" />
</postProcess>

That fuseaction will call the “checkLayout” fuse in the circuit “layout”, and it will check if we want to use a layout or which layout template to load.
So, let’s write that “checkLayout” in \circuits\layout\circuit.xml.cfm:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

<? xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE circuit>
<!-- circuit: LAYOUT -->
<circuit access="internal" xmlns:cf="cf/">
<fuseaction name="checkLayout">
<set name="request.useLayout" value="default" overwrite="false" />
<if condition="request.useLayout is 'default'">
<true>
<include template="layDefault" required="true" />
</true>
</if>
<if condition="request.useLayout is 'brochure'">
<true>
<include template="layBrochure" required="true" />
</true>
</if>
</fuseaction>
</circuit>

First we set a default value for the variable “request.useLayout” with the attribute “overwrite” to “false” because we don’t want overwrite it in case it already exists.

Then we start checking for its value, if it is “default”, include the default template, if it is “brochure” then include the brochure layout template, and so on (you may have as many layouts you want).

Have you noticed that you do not need to write the file extension .cfm for the template names in the <include> tag? Fusebox will assume you are loading ColdFusion templates if you do not specify the file extension.

Now that we have the header, footer and layout calls, let’s work on the default layout template in \circuits\layout\layDefault.cfm:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

<cfparam name="content.header" default="This is the Header" />
<cfparam name="content.footer" default="This is the Footer" />
<cfparam name="content.mainContent" default="This is the main content" />
<cfparam name="request.pageTitle" default="FPTutorial" />
<html>
<head>
<cfoutput><title>#request.pageTitle#</title></cfoutput>
</head>
<body>
<cfoutput>
<p>#content.header#</p>
<p>#content.mainContent#</p>
<p>#content.footer#</p>
</cfoutput>
</body>
</html>

Run your application and you should receive a page like Figure 2.2.

Figure 2.2

On the next part of this tutorial we will work with some content for the main page, to replace the “Hello World”.

The idea is to make you comfortable with the framework showing where to add fuses, variables, include templates, etc.

Just keep in mind that if you are using layouts, you must create all your content, save it to variables before Fusebox finishes processing and throwing the layout page.

Thank you for your interest and feel free to write any comment to this post.

Download here the zip file with the files for this tutorial. Please note that the fusebox.xml.cfm contain commented circuits for future development.

I work with Fusebox framework since its version 2. Now we are at version 5.51. I decided to write this tutorial to help some friends who haven’t got into Fusebox yet but are anxious to jump into the bandwagon, just don’t know how to start. I recommend Jeff Peter’s books on Fusebox for those who really want to take advantage of this framework:

• Fusebox 5 & Flip Master-Class ColdFusion Applications
• How to Drive Fusebox 5.5

MVC – Model View Controller

Before going into the framework, let’s talk a little about MVC (Model, View, Controller). For those who don’t know MVC, it is a method of separating the presentation, action and control layers of the application in order to achieve better and secure way of programming, and easier maintenance.

All external calls (from the web URL) are directed to the Control layer. Then the Control will decide which actions to take, like performing a query, a calculation, etc… That is done in the Model layer, which has no access from the outside world. Then the Control will submit the results to the View (presentation layer) which will assemble the contents to the public. Basically, all public link addresses to your website will be calling the Control layer. All your queries and action pages will be in the Model, and all your display pages will be in the View, easy to find and maintain.

Example: if you have to show a list of real estate properties, the Control will call a query in the Model to obtain the data and then call a display page in the View to show all the properties selected in the query.

Fusebox

Figure 1.1

Fusebox is a methodology for developing web applications. It protects your application by forcing all calls to be made to a single template: index.cfm, which acts as the hub where all connections are made. By passing the “fuseaction” attribute, you will tell the Fusebox framework what action you want to be executed.

So, with the analogy to the “electric fusebox”, the framework is divided into “circuits” and “fuses”. Your application folders are called “circuits” and the ColdFusion templates are the “fuses”.

In this tutorial we will be referencing the Fusebox 5.51 XML version, not the non-xml one (sort of OO). Let’s start by downloading the Fusebox 5.51 Core Files, select the first link: Official FB5.5.1/CFMX core files (v5.5.1).

Unzip the contents to a folder named “fusebox5″ inside your web application root if you DO NOT have access to the ColdFusion administration site. Otherwise, extract the contents to a folder outside your web root and then map it as “/fusebox5″. Doing that, you will be able to have multiple websites using the same Fusebox core installation.

Your Fusebox core structure should be like Figure 1.1 side.

Figure 1.2

We are going to create a web application for a store called FBTutorial. Here are the initial application requirements:

• Home Page with News Articles
• Contact Page – form
• Products page – catalog
• Shopping Cart

Figure 1.3

I know two ways of creating the MVC structure for a Fusebox application. One is most used by creating 3 folders: _model, _view and _controller (the underscores are for placing the folders on top of the other regular ones), and inside those folders we would put the Fusebox circuits.

I find that more complicated and less modular. Any maintenance you need to do, you will have to look at the subfolders inside other subfolders, etc… (figure 1.3)

If you want to turn a circuit into a module that could be copied to other application, the better approach should be creating the circuits first, and then inside each circuit you create the folders “model” and “view”, being the circuit root itself working as the “controller”.

So I chose the second structure by creating the circuit folders and

Figure 1.4

then their subfolders model and view (Figure 1.4). Here is how we will create the application structure:

• FBTutorial
  • circuits
    • forms
    • home
    • news
    • products
    • shopping
  • other folders…

Now, inside each circuit folder, we will create the folders “model” and “view“. You decide

Figure 1.5

if you want to prefix them with underscore “_”, since you will not have any other folder in the circuits.

After creating all the necessary folders, we need to create empty control files in each folder. Those files will be named “circuit.xml.cfm”, which are XML files but with the extention CFM so they cannot be read by the browser without being parsed by ColdFusion. Just create the empty files for now.

Figure 1.5 shows the new structure with the XML files.

Do not worry about the empty files, we will fill them in later.

Figure 1.6

I’m just preparing the application structure before starting coding.

Now, let’s create the Fusebox required and optional files on the application root. Starting with the Application.cfc (capital “A”), fusebox.appinit.cfm, fusebox.init.cfm, fusebox.xml.cfm and index.cfm (create those empty files and we’ll work on them next. Your structure now should be like Figure 1.6.

Application Root

Let’s start now working on the Fusebox files on the application root. First of all, the Application.cfc component which is always the first to run on each request.
The basic methods in the Application.cfc component are:

• onApplicationStart,
• onApplicationEnd,
• onSessionStart,
• onSessionEnd,
• onRequestStart

You may have additional methods like onRequestEnd, onError… but right now we are interested in the Fusebox method: onFuseboxApplicationStart. That method is called when the Fusebox application initiates. It replaces the template fusebox.appinit.cfm in the application root. So if you may decide to use this method instead of that template, then it’s one less file to maintain.

Here is our Application.cfc template:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121

<cfcomponent extends="fusebox5.Application" output="false">
<cfscript>
this.name = right(REReplace(expandPath('.'),'[^A-Za-z]','','all'),64);
this.applicationTimeout = createTimeSpan(0,6,0,0);
this.sessionManagement = true;
this.sessionTimeout = createTimeSpan(0,0,30,0);
this.clientManagement = true;
this.mainDSN = "myDSN";
this.webmasterEmail = "myEmail@myDomain.com";
</cfscript>
<!--- trap non-index.cfm requests - must be outside onXxxYyy() handlers --->
<cfif right(cgi.script_name, len("index.cfm")) neq "index.cfm" and
right(cgi.script_name, 3) neq "cfc">
<cflocation url="index.cfm" addtoken="no" />
</cfif>
<cffunction name="onApplicationStart" returntype="boolean" output="false">
<cfreturn True>
</cffunction>
<cffunction name="onApplicationEnd" output="false">
<cfargument name="applicationScope" required="true" />
</cffunction>
<cffunction name="onSessionStart" output="false">
</cffunction>
<cffunction name="onSessionEnd" output="false">
</cffunction>
<cffunction name="onFuseboxApplicationStart">
<cfset super.onFuseboxApplicationStart() />
<!--- code formerly in fusebox.appinit.cfm --->
<cfif not structKeyExists(application,"mainDSN")>
<cflock name="mainDSN" type="exclusive" timeout="10">
<cfset application.mainDSN = this.mainDSN />
</cflock>
</cfif>
</cffunction>
<cffunction name="onRequestStart">
<cfargument name="targetPage" />
<cfscript>
super.onRequestStart(arguments.targetPage);
//code formerly in fusebox.init.cfm
self = myFusebox.getSelf();
myself = myFusebox.getMyself();
if (listFirst(CGI.SERVER_NAME, ".") == "www") {
FUSEBOX_PARAMETERS.mode = "production" ;
} else {
FUSEBOX_PARAMETERS.mode = "development-circuit-load" ;
}
// request scope
request.applicationName = this.name;
request.mainDSN = this.mainDSN;
request.webmasterEmail = this.webmasterEmail;
request.baseDir = GetDirectoryFromPath(GetBaseTemplatePath());
request.componentPath = "assets.components.";
request.imagePath = "assets/images/";
request.cssPath = "assets/css/";
request.jsPath = "assets/js/";
request.flashPath = "assets/multimedia/";
request.videoPath = "assets/multimedia/";
request.ppsPath = "assets/multimedia/";
</cfscript>
</cffunction>
</cfcomponent>

Now, here is the deal. Since the Fusebox core also has an Application.cfc with the same methods, we need to extend our Application.cfc to the Fusebox one and make use of the “call super” to invoke those methods first in order to use ours. On the first line, we extend the component. Remember to map /fusebox5 in your ColdFusion adminstration to the folder were you saved the core files.

1

<cfcomponent extends="fusebox5.Application" output="false">

The method onFuseboxApplicationStart must have the call super:

1
2
3
4
5

<cffunction name="onFuseboxApplicationStart">
<cfset super.onFuseboxApplicationStart() />
… … …

onRequestStart should have also the call super:

1
2
3
4
5
6
7
8
9

<cffunction name="onRequestStart">
<cfargument name="targetPage" />
<cfscript>
super.onRequestStart(arguments.targetPage);
… … …

Some code that was formerly in fusebox.init.cfm:

1
2
3
4
5
6
7
8
9
10
11
12
13

self = myFusebox.getSelf();
myself = myFusebox.getMyself();
if (listFirst(CGI.SERVER_NAME, ".") == "www") {
FUSEBOX_PARAMETERS.mode = "production" ;
} else {
FUSEBOX_PARAMETERS.mode = "development-circuit-load" ;
}

Fusebox.init.cfm

We basically wrote all the necessary code for starting with the Application.cfc, now let’s concentrate on the Fusebox template fusebox.init.cfm. It is included by the framework at the start of every request. It is included within a cfsilent tag so it cannot generate output. It is intended to be for per-request initialization and manipulation of the fuseaction variables.

You can set attributes.fuseaction, for example, to override the default fuseaction. Fusebox 5.1 and later – set variables implicitly from the Fusebox itself.

Could also modify the self location here:

1

<cfset myFusebox.setSelf("/myapp/start.cfm") />

For now, just write the following code in your fusebox.init.cfm template:

1
2
3
4
5

<cfprocessingdirective suppresswhitespace="true">
<!--- some future code here --->
</cfprocessingdirective>

Index.cfm

The index.cfm template will have only one statement:

1

<cfinclude template="/fusebox5/fusebox5.cfm" />

In a Fusebox application the index.cfm template has no use other than to include the framework.

Fusebox.xml.cfm

The last file on the application root we have to work on is the fusebox.xml.cfm, which is the file that controls all the fusebox circuits, parameters, classes, plugins and global actions.
In the “circuits” block we define the paths and aliases for the circuits. You may chose any name as an alias to a circuit, does not have to be the same name of the folder, you will see below that we are calling “cart” the circuit in the folder “shopping”.
The “parameters” block contains Fusebox default settings, and it is customizable.
Here is our fusebox.xml.cfm file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fusebox>
<!--Example fusebox.xml control file. Shows how to define circuits, classes, parameters and global fuseactions. This is just a test namespace for the plugin custom attribute example -->
<fusebox xmlns:test="test">
<circuits>
<!-- Home circuit -->
<circuit alias="home" path="circuits/home/" parent="" />
<circuit alias="mhome" path="circuits/home/model/" parent="home" />
<circuit alias="vhome" path="circuits/home/view/" parent="home" />
<!-- Forms circuit -->
<circuit alias="forms" path="circuits/forms/" parent="home" />
<circuit alias="mforms" path="circuits/forms/model/" parent="forms" />
<circuit alias="vforms" path="circuits/forms/view/" parent="forms" />
<!-- News circuit -->
<circuit alias="news" path="circuits/news/" parent="home" />
<circuit alias="mnews" path="circuits/news/model/" parent="news" />
<circuit alias="vnews" path="circuits/news/view/" parent="news" />
<!-- Products circuit -->
<circuit alias="products" path="circuits/products/" parent="home"/>
<circuit alias="mproducts" path="circuits/products/model/" parent="products" />
<circuit alias="vproducts" path="circuits/products/view/" parent="products" />
<!-- shopping circuit -->
<circuit alias="cart" path="circuits/shopping/" parent="home" />
<circuit alias="mcart" path="circuits/shopping/model/" parent="cart" />
<circuit alias="vcart" path="circuits/shopping/view/" parent="cart" />
<!-- Layout circuit -->
<circuit alias="layout" path="circuits/layout/" />
</circuits>
<classes>
</classes>
<parameters>
<parameter name="defaultFuseaction" value="home.main" />
<!-- you may want to change this to development-full-load mode: -->
<parameter name="mode" value="development-full-load" />
<!-- change this to something more secure: -->
<parameter name="password" value="" />
<parameter name="strictMode" value="true" />
<!-- These are all default values that can be overridden:
<parameter name="fuseactionVariable" value="fuseaction" />
<parameter name="precedenceFormOrUrl" value="form" />
<parameter name="scriptFileDelimiter" value="cfm" />
<parameter name="maskedFileDelimiters" value="htm,cfm,cfml,php,php4,asp,aspx" />
<parameter name="characterEncoding" value="utf-8" />
<paramater name="strictMode" value="false" />
<parameter name="allowImplicitCircuits" value="false" />
<parameter name="debug" value="false" /> -->
</parameters>
<globalfuseactions>
<preprocess>
</preprocess>
<postprocess>
</postprocess>
</globalfuseactions>
<plugins>
<phase name="preProcess">
</phase>
<phase name="preFuseaction">
</phase>
<phase name="postFuseaction">
</phase>
<phase name="fuseactionException">
</phase>
<phase name="postProcess">
</phase>
<phase name="processError">
</phase>
</plugins>
</fusebox>

We define the circuits in the “circuits” block by assigning an alias to the path. In the application we will call the index.cfm passing the circuit,fuse and fuseaction we want to execute. Example:

Figure 1.7

index.cfm?fuseaction=home.main
index.cfm?fuseaction=products.showProduct&productID=1234
index.cfm?fuseaction=cart.addToCart

With Fusebox, everything is assembled in the root. The index.cfm loads Fusebox and it prepares the request to be served without the customer seeing in which folders the templates are.
We added a circuit named “layout” which will handle all the layouts for our application. Since it is for the presentation layer, we do not have to create the “model” folder. Figure 1.7 shows an updated version of our structure.

Circuit.xml.cfm

Now we are going to look at the circuit.xml.cfm file placed in all circuits.
Let’s start with the “home” main circuit, the controller one” /circuits/home/circuit.xml.cfm:
For now we will not have any actions to call, just a display page to show the homepage, then our circuit.xml.cfm file will have the following code:

1
2
3
4
5
6
7
8
9
10
11
12
13

<?xml version="1.0" encoding="UTF-8"?>
<!-- home -->
<circuit access="public" xmlns:cf="cf/">
<fuseaction name="main">
<do action="vhome.main" />
</fuseaction>
</circuit>

You noticed that we here we are calling an action on another circuit, the “vhome”, in the “view” part of the MVC, to display the homepage. If we had to calculate anything or grab any information from a database in order to populate that homepage, then we would call the “model” layer before the “view”.

The call to “index.cfm?fuseaction=home.main” will get to this circuit which will call the “vhome.main” fuseaction in the “view” area. Subsequently that fuseaction, “vhome.main”, will include the template “dspMain.cfm” with the contents of the homepage, and then Fusebox will assemble the full page for ColdFusion to render to the browser. Note that the attribute “access” for this circuit is set to “public”. That means it can be accessed by the web browser, it is a public fuse.

Here is the circuit.xml.cfm file in the “view” area:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE circuit>
<!-- vhome -->
<circuit access="internal" xmlns:cf="cf/">
<fuseaction name="main">
<include template="dspMain.cfm" required="true" />
</fuseaction>
</circuit>

In this case, the “access” attribute is set to “internal” which means this circuit can be only called by another circuit, it will not respond to browser calls.

The fuseaction “main” will include the template dspMain.cfm.
Just for testing purpose, create the file dspMain.cfm with the following HTML code:

1

<h1>Hello World</h1>

Now, let’s test the site. If you have ColdFusion Developer Edition installed in your machine, just browse to: “http://localhost/FBtutorial“. You do not have to specify any attributes, because the Fusebox configuration file (fusebox.xml.cfm) will take care of calling the default fuseaction “home.main”.
You should get the page “Hellow World”.

On the next part we will start handling layouts.

I hope you have liked this tutorial and please feel free to comment if you have questions.

Part 2

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=1489920&loc=en_us

Read it here: http://blog.kukiel.net/2011/08/how-to-upgrade-coldfusion-builder-2-to.html

Caching is such a deep and complex subject that it can be difficult to know where to begin. This session will cover the basics of caching in ColdFusion from using page and query caching to using CFCs to cache data and functions into a persistent scope to create a service, as well as the new caching functions in ColdFusion9. We will discuss the pros and cons of each solution and workarounds for caching and refreshing the cache as you need it. You’ll be amazed at the difference caching can make for your websites.
MEETING URL:
http://experts.acrobat.com/cfmeetup/
DURATION: Approx. 1 hour
RECORDING: All meetings are recorded. The URL will be posted after meeting at

recordings.coldfusionmeetup.com

SPEAKER: (provided by the speaker)

Daria Norris is a Web Developer for the Free Library of Philadelphia, where she develops custom library applications. Her biggest project is a search engine of 20K digital images from the library’s scholarly collections including medieval manuscripts, historical photographs, maps and more. She has been a ColdFusion developer for 15 years, getting her start in a corporate library where she developed a checkout system that evolved into a Competitive Intelligence search engine. Her passion is making information easier to find and plans to return to school to finish a double masters degree in Information Systems and Library Science.
WHEN: Thurs. August 11, 12:00pm
US ET (UTC/GMT-4)
What time is that for you? The following link shows . Here’s that shows the time as US ET, and lets you choose your city from the list offered to see what time that is in your own timezone.
DOWNLOADABLE RECORDINGS:

In addition to the streaming recording posted immediately after the meeting, we now also post recordings at usually within a day of the meeting.
LOGGING IN: When you login to the Connect room (the experts.acrobat.com/cfmeetup link above) to view the meeting, PLEASE USE THE “LOGIN AS GUEST” option, and USE YOUR NAME, but do NOT attempt to use your meetup.com username/password or any Connect account. Just sign in as a guest.
RSVP, but only if coming: We do appreciate folks RSVPing if they plan to come (using the link on this email or at the meetup site), though it’s not mandatory and it’s not a commitment. But there’s
no need to RSVP if you can’t make it let alone explain why you can’t. With over 2,600 members, no worries.
FEEDBACK/MEETING DISCUSSION: Members will receive an email after the meeting or can click a link on the event page to offer. Note also the meeting-specific discussion area there at the bottom, in addition to the one-chance feedback feature on the right. Feel free to engage in discussions about the meeting topic.
ADD THIS TO YOUR CALENDAR: Want to add this event to your own personal calendar?

After logging in here
, you’ll see an option at the top of the event page, just below the event title, saying, “Export”, which offers calendar downloads for Outlook, iCal, Google, and Yahoo calendars. (Note that the calendar entry created will show the event taking 2 hours. That’s a default that meetup.com has chosen, which I can’t change. The meetings are generally about an hour, though often go as much as 30-45 minutes longer with Q&A and chat.)

Learn more