A note about multiple regions in ADF 11g

Well, most of ADF applications have a need to have multiple regions on a single page. For each task flow dropped on the ADF page, an entry is created in the page definition file.

At the run time, ADF framework looks into the page definition file and tries to execute/initialize all the regions. This is true even if you set the render property of the region in your page to false. At times, this may not be desirable and in some cases this could create problems for you. Every region entry in the page definition comes up with a property called activation which has default value 'immediate'. So, to avoid un-necessary execution of a region you can change it to value 'conditional'. And in the next to it property active you can specify an EL expression with a condition to execute that region.