PanelCollection Confusion ... or, what is an event root ?
- by frank.nimphius
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
A command button added to the toolbar of a Panel Collection
component does not cause field validation in a form when pressed. While this
appears confusing it works as designed.
Instead of a full page re-rendering, ADF Faces events and
components can trigger partial page refresh, in which only portions of a page are
refresh upon a request. In addition, some components - including the af:popup
and af:subForm - represent event roots. Event roots don't propagated event
notification outside of the component tag boundary, which means that the ADF
Faces lifecycle only executed on components that are children of the event root
component. The PanelCollection component is an event root and therefore only
validates and refreshes data of its child components.
