TIP # 1. How to find the backing bean of an ADF Page ?
(In OAF, it is very easy to get the CO name which is used in a given page/region).
In ADF -- Controller logic is handled through Taskflows.
For a given page : check the below way to get which Controller(Taskflow) is used.
Following is the page and its managed bean information.
Following is the screen for the Page file.
Following is the content of page file in XML Code.
In the below code : (if you compare with OAF - which is based on UIX-User interface for XML) -- This is based jspx ; xml with jsp.
Top level bean in JSPX is : JSP:Root followed by : f:view
<f:view>
<af:document id="d1" binding="#{backingBeanScope.backing_ADFRegionsPG.d1}">
<af:form id="f1" binding="#{backingBeanScope.backing_ADFRegionsPG.f1}"></af:form>
</af:document>
</f:view>
In f:view -- other tag is : af:document
this is attached to bean -- This is bean which is attached to this page.
CTRL+CLICK on : ADFRegionsPG.d1 -- Navigates to ADFRegionsPG.java
Backing bean information : about : package, class details of it.
(In OAF, it is very easy to get the CO name which is used in a given page/region).
In ADF -- Controller logic is handled through Taskflows.
For a given page : check the below way to get which Controller(Taskflow) is used.
Following is the page and its managed bean information.
Following is the screen for the Page file.
Following is the content of page file in XML Code.
In the below code : (if you compare with OAF - which is based on UIX-User interface for XML) -- This is based jspx ; xml with jsp.
Top level bean in JSPX is : JSP:Root followed by : f:view
<f:view>
<af:document id="d1" binding="#{backingBeanScope.backing_ADFRegionsPG.d1}">
<af:form id="f1" binding="#{backingBeanScope.backing_ADFRegionsPG.f1}"></af:form>
</af:document>
</f:view>
In f:view -- other tag is : af:document
this is attached to bean -- This is bean which is attached to this page.
CTRL+CLICK on : ADFRegionsPG.d1 -- Navigates to ADFRegionsPG.java
Backing bean information : about : package, class details of it.
No comments:
Post a Comment