Saturday, August 31, 2013

ADF UI: Regions

  • Display as independent areas of ADF Faces View (Page - Page Fragment).
  • Regions Type:
    • Dynamic: Many task flow according to managed bean "used in UI shell layout".
    • Static: Use always the same task flow.
  • You can only start with a same page in single task flow but that not mean you must start with the same region every time "you can pass parameters to specify start region" in this page.
  • Region Integrates:
    • ADF Faces 'af:region' tag.
    • Bounded task flow (serious of navigation tabs between fragments).
    • Managed bean (optional "if dynamic region") using method to select region.
    • PageDef (file contains region)
    • Page fragments (views use in regions)
  • Create an ADF Region:
    • Drag bounded task flow to visual page editor.
    • Select 'Region' or 'Dynamic Region'
  • Static Region binds to single task flow at design time.
  • Binding Attributes:
    • taskflowId: Reference "Path" to task flow definition
    • Parameters Map: Allow Parameters to be passed in HashMap [Managed Bean].
    • Activation:
      • Deferred: if region not visible, it will not load until its become visible.
      • Conditional: EL to when its active task flow
      • Immediate: will initialize whatever its not visible
    • Active: EL provides to conditional activation
  • ADF Region Input Parameters: 
    • Specify through property inspector in task flow binding reference.
  • When ADF Regions are Refreshed:
    • During the initial rendering of the ADF region
    • When the referenced task flow ID changes, which is the dynamic ADF region usecase
    • When the 'af:region' component  recieves a PPR notification & the task flow binding of the ADF region is refereshed
      • refresh condition
      • refresh Option
    • When the refresh method on the RichRegion instance is called in a manged bean. 
  • ADF Region Interaction Problem:
    • Establish communication without breaking ADF Region encapsulation if reuse is a goal.
    • Tight coupling [multiple term & each have module].
    • Making assumption about the ADF Region context.
  • Interactions:
    • Parent View to ADF Region
    • ADF Region to Parent View
    • ADF Region to ADF Region

No comments:

Post a Comment