Site Configuration (ADF.cfc) - Revision history

Gcronkright: /* ADF Site Dev Mode */

2014-12-06T02:54:11Z

‎ADF Site Dev Mode

Gcronkright: /* ADF Site Dev Mode */

2014-12-06T02:48:13Z

‎ADF Site Dev Mode

Gcronkright at 02:47, 6 December 2014

2014-12-06T02:47:23Z

Gcronkright: /* Overview */

2014-12-06T02:39:40Z

‎Overview

Rwest: Reverted edits by Ecaxabu (Talk) to last revision by Rwest

2010-11-24T17:40:40Z

Reverted edits by Ecaxabu (Talk) to last revision by Rwest

Ecaxabu at 23:04, 23 November 2010

2010-11-23T23:04:38Z

Rwest: moved Site Level ADF Component to Site Configuration (ADF.cfc)

2010-04-15T04:31:27Z

moved Site Level ADF Component to Site Configuration (ADF.cfc)

Rwest: moved Site Configuration to Site Level ADF Component

2010-04-05T04:50:06Z

moved Site Configuration to Site Level ADF Component

Rwest at 04:49, 5 April 2010

2010-04-05T04:49:24Z

Mcarroll at 14:13, 26 March 2010

2010-03-26T14:13:14Z

@@ Line 39: / Line 39: @@
 === ADF Site Dev Mode ===
-By default the ADF runs with development mode disabled (false) to enable set to (true). Production mode, development mode disabled, is highly recommended for public facing sites. Development mode opens up more robust exception handling messages for ajaxProxy and lightboxProxy javascript requests.
+By default the ADF runs with development mode disabled (false) to enable set to (true). Production mode (development mode disabled) is highly recommended for public facing sites. Development mode opens up more robust exception handling messages for ajaxProxy and lightboxProxy javascript requests.
 <pre>
 /*

@@ Line 39: / Line 39: @@
 === ADF Site Dev Mode ===
-By default the ADF runs with development mode disabled (false) to enable set to (true). Production mode, development mode disabled, is highly recommended for public facing sites. Development mode opens up more robust exception handling message for ajaxProxy and lightboxProxy javascript requests.
+By default the ADF runs with development mode disabled (false) to enable set to (true). Production mode, development mode disabled, is highly recommended for public facing sites. Development mode opens up more robust exception handling messages for ajaxProxy and lightboxProxy javascript requests.
 <pre>
 /*

@@ Line 18: / Line 18: @@
   */
 loadSite();
 </pre>

@@ Line 10: / Line 10: @@
 This initialized call builds the ''application.ADF'' object factory.  This function will load any site components in the '_cs_apps/components' directory into 'application.ADF' space.  The structure reference name will be the file name of the component.
-<source lang="java">
+<pre>
 /*
+  *
@@ Line 18: / Line 18: @@
   */
 loadSite();
-</source>
+</pre>
 === ADF Applications ===
@@ Line 24: / Line 24: @@
 This setup is in the ADF Component at the site.  Call the loadApp function through the ADF cfc.  Pass the argument for the ADF application bean name  (this name is defined when creating a new ADF application, [[Create_New_App|Create New ADF App]]).
-<source lang="java">
+<pre>
 /*
   *	Load the ADF Application into application space
@@ Line 32: / Line 32: @@
   */
 loadApp("ptProfile");
-</source>
+</pre>
 === ADF Library Components ===
 This command will load the latest versions of the ADF library components into the site, making the ADF library components accessible through the application.ADF scope throughout the site.
-<source lang="java">
+<pre>
 /*
+  *
@@ Line 43: / Line 43: @@
   */
 loadLibrary();
-</source>
+</pre>
 === ADF Library Components Overrides ===
 This command will override the latest version of an ADF library component into the site.
-<source lang="java">
+<pre>
 /*
   *	Define specific ADF Lib component version to load into the sites application space.
@@ Line 56: / Line 56: @@
   */
 resetLibrary("csdata_1_0", "csdata");
-</source>
+</pre>
 == Verify ==

@@ Line 1: / Line 1: @@
 == Overview ==
 A key part of the configuration of the ADF for your site is the ADF.cfc located in your sites /_cs_apps/ directory (e.g. /mySite/_cs_apps/ADF.cfc).
@@ Line 18: / Line 10: @@
 This initialized call builds the ''application.ADF'' object factory.  This function will load any site components in the '_cs_apps/components' directory into 'application.ADF' space.  The structure reference name will be the file name of the component.
-&lt;source lang=&quot;java&quot;&gt;
+<source lang="java">
 /*
+  *
@@ Line 26: / Line 18: @@
   */
 loadSite();
-&lt;/source&gt;
+</source>
 === ADF Applications ===
@@ Line 32: / Line 24: @@
 This setup is in the ADF Component at the site.  Call the loadApp function through the ADF cfc.  Pass the argument for the ADF application bean name  (this name is defined when creating a new ADF application, [[Create_New_App|Create New ADF App]]).
-&lt;source lang=&quot;java&quot;&gt;
+<source lang="java">
 /*
   *	Load the ADF Application into application space
+  *
   *      SAMPLES:
-  *		loadApp(&quot;CustomAppBeanName&quot;);
+  *		loadApp("CustomAppBeanName");
   */
-loadApp(&quot;ptProfile&quot;);
+loadApp("ptProfile");
-&lt;/source&gt;
+</source>
 === ADF Library Components ===
 This command will load the latest versions of the ADF library components into the site, making the ADF library components accessible through the application.ADF scope throughout the site.
-&lt;source lang=&quot;java&quot;&gt;
+<source lang="java">
 /*
+  *
@@ Line 51: / Line 43: @@
   */
 loadLibrary();
-&lt;/source&gt;
+</source>
 === ADF Library Components Overrides ===
 This command will override the latest version of an ADF library component into the site.
-&lt;source lang=&quot;java&quot;&gt;
+<source lang="java">
 /*
   *	Define specific ADF Lib component version to load into the sites application space.
+  *
   *	SAMPLE:
-  *		resetLibrary(&quot;csdata_1_0&quot;, &quot;csdata&quot;);
+  *		resetLibrary("csdata_1_0", "csdata");
+  *
   */
-resetLibrary(&quot;csdata_1_0&quot;, &quot;csdata&quot;);
+resetLibrary("csdata_1_0", "csdata");
-&lt;/source&gt;
+</source>
 == Verify ==

← Older revision	Revision as of 04:31, 15 April 2010
(No difference)

← Older revision	Revision as of 04:50, 5 April 2010
(No difference)