Difference between revisions of "Site Level ADF Library Components Overrides"
From ADF Docs
(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…') |
|||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| − | Customization at the site level for a ADF application is | + | 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. |
== Override ADF Library Components == | == Override ADF Library Components == | ||
| − | To override the ADF library components at the site level, | + | 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]] | ||
Revision as of 23:36, 19 December 2009
Overview
Customization at the site level for a ADF application is available: sites can run a 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.
Override ADF Library Components
To override the ADF library components at the site level, the same process as the Custom Application ADF Library Overrides is used.
[Category: Customization]]
