OAF_OAF Architecture MVC Series-Overview of view (concept)

2014-06-18 Baoxinjian

I. Summary

Described above in oaf according to the MVC architecture, divided into three layers, namely Model-view-contorl, on the oaf View layer of the basic concepts and some small cases

• Page-Overview of pages
  • Key Properties for page
  • Key properties of item
• Reusable component-Reusable components
  • control's inheritance Extend
  • control's share shared
• Attribute Sets-control property Group
  • Manually set by the attribute set property of item
  • Automatic code control via Attrset.setattributevalue ()/Getattributevalue ()
• URL Parameters-Link parameters
  • A simplest Possible Expression Language (spel) syntax
  • Five grammatical structures
    {! ATTR}
    {@Attr}
    {$Attr}
    {@ @RETURN_TO_MENU}
    {@ @RETURN_TO_PORTAL}
• Style Sheets-styles sheet
  • Item Type you need to set some relationships for the default CSS to confirm the structure of the CSS
    • Item Type (staticstyledtext), CSS Class (Orainstructiontext)
    • Item Type (Text entry fields, checkboxes, Poplists and radio buttons), CSS Class (Orafieldtext)
    • Item Type (messagestyledtext), CSS Class (Orainstructiontext)
• Integration of model Interaction-view and model
  • View reading the data in model
  • View Write data in model

Second, the specific analysis

1. Page-Overview

When you create a oaf, you typically create page-by-Region-items

Some key properties of the 1.1 Page

• AM Definition:
  • Function: Defines the root application Model used,
  • Example: Oracle.apps.fnd.framework.toolbox.tutorial.server.SearchAM-the page is using Searcham,am with Vo, vo associated with SQL and EO, Which limits what the page can reference.
• Window Title
  • Role: The title of the Windows window
• Title
  • Role: Title of the page
• Form
• Help Target
  • Role: Show Help link on page
  • Example: Set to True
• Autofooter
  • Role: Footer under Page
  • Example: Set to True
• pagelayout Components
  • Role: All the space in the page, the most complex concept in page, involves a lot of controls, another article describes

Some key properties of the 1.2 Item

• Extends: Whether the inherited class has references
• Attribute set: Whether a referenced property group
• Destination URI: Hyperlink property, when defining a parameter, the language used is Spel
• Action Type: Action is present
  • Action Type
  • Event
  • Parameter
• CSS Class: Whether to have a referenced style sheet
• View Instance/view Attribute: Whether the field is taken from data vo, if yes, the fields that define VO and Vo
• Admin/user Personalization: Whether personalization is enabled
• Inital Value: Initial value

1.3 Spel language

OAF the Spel (simplest Possible Expression Language) language is used when defining parameters in the page URL or in action arguments

For example, in action, parameter refers to a parameter on the page: ${oa. Viewinstancename.viewattributename}

2. Reusable components-Reusable component

Each development language involves the common and inherited nature of some components,

2.1 Common nature:

• Shared regions
• Shared Pages
• Shared Items
• Shared Logistic

2.2 Inheritance:

Another article introduces

2.3 Special Examples-LOV

Lov embodies the existence of both common and inherited

• When defining Lov region, you need to define it as public

• In the item reference to the Lov, you must extend the Lov

3. Attribute sets-control property Group

3.1 Manually set by the attribute set property of item

Oracle Default AttributeSet storage location:/oracle/apps/fnd/attributesets/

3.2 Automatic Code control via Attrset.setattributevalue ()/Getattributevalue ()

public void ProcessRequest (Oapagecontext pagecontext, Oawebbean Webbean) {
Super.processrequest (PageContext, Webbean);
AttributeSet Attrset =
New AttributeSet (PageContext, "/oracle/apps/fnd/attributesets/buttons/create");
String createprompt = (string) attrset.getattributevalue (PageContext, prompt_attr);
}

4. URL Parameters-Link parameters

The URL parameters is implemented when the page is in hyperlink-pass parameter

Like oa.jsp? oafunc=fwk_tbx_t_po_page&order={@OrderNum}, you can use the Ordernum parameter on the next page

This is a kind of simplest Possible Expression Language (spel) syntax

Five grammatical structures

• {! ATTR}
• {@Attr}
• {$Attr}
• {@ @RETURN_TO_MENU}
• {@ @RETURN_TO_PORTAL}

5. Style Sheets-style sheet

Item Type needs to set some relationship of the default CSS to confirm the structure of the CSS, so as to control the display consistency of the control, input item has the input CSS style, display the item has the display CSS style, actually is the page and the control style

• Item Type (staticstyledtext), CSS Class (Orainstructiontext)
• Item Type (Text entry fields, checkboxes, Poplists and radio buttons), CSS Class (Orafieldtext)
• Item Type (messagestyledtext), CSS Class (Orainstructiontext)

6. Model Interaction-view and model integration

6.1 View reading the data in model

When the system reads the data, it is actually by reading the current view Object rowimp corresponding EO getattributename to achieve

It's a relatively clear demonstration.

6.2 View Write the data in model

When the system writes the data, it is actually by reading the current view Object rowimp corresponding EO setattributename to achieve

It's a relatively clear demonstration.

Thanks and regards