App Bean Config - Revision history

Dbeckstrom: /* Example */

2010-04-21T16:19:51Z

‎Example

2010-03-30T02:58:45Z

‎Example

2010-03-30T02:09:02Z

‎Overview

2010-03-30T02:00:58Z

‎Example

2010-03-30T01:59:11Z

‎Example

2010-03-30T01:40:09Z

‎Related Guides

2010-03-30T01:39:12Z

‎Sample coding

2010-03-30T01:38:30Z

2010-03-30T01:12:17Z

2010-03-26T14:37:15Z

@@ Line 37: / Line 37: @@
 == Example ==
-Lets say you are building a new Twitter application your application may contain the following code:
+Lets say you are building a new Twitter application.  Your application may contain the following code:
 * /ADF
 ** /apps - contains all installed [[ADF Application]](s)

@@ Line 53: / Line 53: @@
 A sample appBeanConfig.cfm would look like this:
-<source line="GESHI_FANCY_LINE_NUMBERS" lang="java">
+<source line="GESHI_FANCY_LINE_NUMBERS" lang="cfm">
 <cfscript>
   // App specific variables
@@ Line 90: / Line 90: @@
 Essentially, what the appBeanConfig.cfm allows you to do is to easily call your application and specific versions of the ADF Libarary components within your application code.  So for instance, if your twittyDAO.cfc contained a function called "addTweet" you could easily write code like this within your appliacation:
-<source lang="java">
+<source lang="cfm">
 <cfscript>
    application.twitty.twittyDAO.addTweet("The CommonSpot ADF is wicked awesome");

@@ Line 1: / Line 1: @@
 == Overview ==
-Each [[ADF Application]] must contain an App Bean Config (appBeanConfig.cfm) in the root of the Applications folder (e.g. /ADF/apps/myApp/appBeanConfig.cfm).
+Each [[ADF Applications|ADF Application]] must contain an App Bean Config (appBeanConfig.cfm) in the root of the Applications folder (e.g. /ADF/apps/myApp/appBeanConfig.cfm).
 The App Bean Config is the ADF Application's configuration file for the LightWire object factory.  This file establishes the bean (components) that you want to use within your application.  The App Bean Config will contain application-specific components in addition to ADF library components.

@@ Line 76: / Line 76: @@
 </source>
-* We first give the App a name.  This must be a unique name that must not be in use ([[Determining ADF Application Name]]).
+* On line 3 we give the App a name.  This must be a unique name that must not be in use ([[Determining ADF Application Name]]).
-* We then load the Applications' [[ADF Application Core Component|App.cfc]] into the [[Glossary|Object Factory]] using the name provided (e.g. "twitty")
+* On line 8 we load the Applications' [[ADF Application Core Component|App.cfc]] into the [[Glossary|Object Factory]] using the name provided (e.g. "twitty")
   Note: the "addSingleton()" method call essentially tells the Object Factory about this component
-* Adding the Site level components is a two step process 1) Register the component with the Object Factory (addSinglton) and 2) Inject the component into the application (more on the value of injecting components later in this page)
+* On lines 11-14 we are adding the Site level components.  This is a two step process 1) Register the component with the Object Factory (addSinglton) and 2) Inject the component into the application (more on the value of injecting components later in this page)
-* Finally, we inject some ADF Library Components into the application (specifying which versions we want to use)
+* Finally, on lines 17-19 we inject some ADF Library Components into the application (specifying which versions we want to use)
 === Injection and Singltons ===

@@ Line 53: / Line 53: @@
 A sample appBeanConfig.cfm would look like this:
-<source lang="java">
+<source line="GESHI_FANCY_LINE_NUMBERS" lang="java">
 <cfscript>
   // App specific variables

@@ Line 97: / Line 97: @@
 == Related Guides ==
 * [[ADF Applications]]
 * [[Building an ADF Application]]

@@ Line 45: / Line 45: @@
 ***** twittyService.cfc - service based CFC component
 ***** twittyDAO.cfc - data access object
-**** appBeanConfig.cfc - configuration of your applications components
+**** /customcf - custom script code for your application

@@ Line 2: / Line 2: @@
 The App Bean Config is the ADF application configuration file for the LightWire object factory.  This file establishes the bean configuration with application-specific components and ADF library components.
-The App Bean Config must have the file name 'AppBeanConfig.cfm' and be located at the root of the ADF application directory.
+The App Bean Config must have the file name '''AppBeanConfig.cfm''' and be located at the root of the ADF application directory.
 == Architecture ==