Site Level ADF Library Components Overrides - Revision history

Mcarroll: /* Best practices */

2011-04-06T17:19:06Z

‎Best practices

Jrybacek: /* Steps to override */

2010-06-22T21:40:22Z

‎Steps to override

Mcarroll: /* Steps to override */

2010-04-08T19:00:33Z

‎Steps to override

Mcarroll: /* Best practices */

2010-04-08T18:59:45Z

‎Best practices

Mcarroll: /* Steps to override */

2010-04-08T18:59:15Z

‎Steps to override

Rwest at 01:09, 8 March 2010

2010-03-08T01:09:11Z

Rwest: moved Custom Application Site Level Customization to Site Level ADF Library Components Overrides: Moved page to a better name

2010-03-08T00:57:27Z

moved Custom Application Site Level Customization to Site Level ADF Library Components Overrides: Moved page to a better name

Renee.mckechnie: /* Override ADF Library Components */

2009-12-19T23:36:59Z

‎Override ADF Library Components

Renee.mckechnie at 23:36, 19 December 2009

2009-12-19T23:36:45Z

Renee.mckechnie: Created page with '== Overview == Customization at the site level for a ADF application is provided. The sites can run a Site Application Bean Configuration for th…'

2009-11-22T03:27:37Z

Created page with '== Overview == Customization at the site level for a ADF application is provided. The sites can run a Site Application Bean Configuration for th…'

New page

== Overview ==
Customization at the site level for a ADF application is provided. The sites can run a [[Site_Application_Bean_Config|Site Application Bean Configuration]] for the ADF application. A unique bean for the ADF application and site name will be generated. This provides the capability to run the same ADF application with different configurations in multiple sites.

== Override ADF Library Components ==
To override the ADF library components at the site level, this is the same process as the [[Custom Application ADF Library Overrides|Custom Application ADF Library Overrides]].

@@ Line 32: / Line 32: @@
 == Best practices ==
-You don't have to override the entire component, you can add new methods and override existing methods pretty easily.  Using the above example, lets say you wanted to add a new function to the component. A sample of your date_1_0 (located in the /mySite/_cs_apps/components/lib/ directory) would look like this:
+You don't have to override the entire component, you can add new methods and override existing methods pretty easily.  Using the above example, lets say you wanted to add a new function to the component. A sample of your date_1_0 (located in the /mySite/_cs_apps/lib/ directory) would look like this:
 <source lang="cfm">
 <cfcomponent displayname="date" extends="ADF.lib.date.date_1_0">

@@ Line 24: / Line 24: @@
 <source lang="cfm">
 <cfcomponent extends="ADF.lib.date.date_1_0">
 </source>

@@ Line 18: / Line 18: @@
 # Copy your ADF Library Component from its directory and place it into your /mySite/_cs_apps/lib/ directory
 # Modify the <cfcomponent> tag to extend the original ADF Library Component.  For example, if you wanted to modify date_1_0.cfc in your application the <cfomponent> tag would be changed from this:
+<source lang="cfm">
- <cfcomponent extends="ADF.core.Base">
+<cfcomponent extends="ADF.core.Base">
+</source>
 to:
+<source lang="cfm">
- <cfcomponent extends="ADF.lib.date.date_1_0">
+<cfcomponent extends="ADF.lib.date.date_1_0">
 == Best practices ==

@@ Line 27: / Line 27: @@
 == Best practices ==
 You don't have to override the entire component, you can add new methods and override existing methods pretty easily.  Using the above example, lets say you wanted to add a new function to the component. A sample of your date_1_0 (located in the /mySite/_cs_apps/components/lib/ directory) would look like this:
+<source lang="cfm">
 <cfcomponent displayname="date" extends="ADF.lib.date.date_1_0">
@@ Line 39: / Line 38: @@
 </cfcomponent>
-</pre>
+</source>
 Notice how the value of the "extends" attribute is pointing to the date_1_0 component loaded into the ADF <em>and</em> notice how there are no other methods in this component.  By extending the original date_1_0 component, you automatically gain all of the methods defined in that component - so you need not copy those in.

@@ Line 15: / Line 15: @@
 == Steps to override ==
-# Create a directory called "lib" in your sites "components" directory (e.g. /mySite/_cs_apps/components/lib)
+# Create a directory called "lib" in your sites directory (e.g. /mySite/_cs_apps/lib)
-# Copy your ADF Library Component from its directory and place it into your /mySite/_cs_apps/components/lib/ directory
+# Copy your ADF Library Component from its directory and place it into your /mySite/_cs_apps/lib/ directory
 # Modify the <cfcomponent> tag to extend the original ADF Library Component.  For example, if you wanted to modify date_1_0.cfc in your application the <cfomponent> tag would be changed from this:

@@ Line 1: / Line 1: @@
 == Overview ==
-Customization at the site level for a ADF application is available: sites can run a [[Site_Application_Bean_Config|Site Application Bean Configuration]] for the ADF application.  A unique bean for the ADF application and site name will be generated,  providing the capability to run the same ADF application with different configurations in multiple sites.
+By default the latest version of each ADF Library Component is loaded into your sites Application.ADF memory space which allows you to write code like this in your Render Handlers, Custom Scripts or Custom Field Types:
-== Override ADF Library Components ==
+<pre>
-To override the ADF library components at the site level, the same process as the [[Custom Application ADF Library Overrides|Custom Application ADF Library Overrides]] is used.
+<cfscript>
 [[Category: Customization]]

← Older revision	Revision as of 00:57, 8 March 2010
(No difference)

← Older revision		Revision as of 23:36, 19 December 2009
Line 5:		Line 5:
	To override the ADF library components at the site level, the same process as the [[Custom Application ADF Library Overrides\|Custom Application ADF Library Overrides]] is used.		To override the ADF library components at the site level, the same process as the [[Custom Application ADF Library Overrides\|Custom Application ADF Library Overrides]] is used.

−	[Category: Customization]]	+	[[Category: Customization]]