The control of the ADF is dragged out by VO. If the same VO is dragged into a Form and a Table on a Page, and the interaction is realized, if there is no data in the VO:
The control of the ADF is dragged out by VO. If the same VO is dragged into a Form and a Table on a Page, and the interaction is realized, if there is no data in the VO:
A page in the Oracle ADF allows you to maintain a region Form and view a region Table.
[Date: 2012-02-03] Source: Linux Author: haqer0825 [Font:]
The control of the ADF is dragged out by VO.
Therefore, if you drag the same VO into a Form and a Table on a Page, and implement Association
If there is no data in VO: The Table shows no data, while the Form control does not display the outer box of the control, and the location is ugly.
Several implementation schemes are as follows:
1. Page A only has A Table. If you need to edit or create A new Table, jump to Page B. As A result, createRow has been added to VO and the maintenance area control has A box
2. If the same page has Form and Table, add a blank row to the initial method-call. The disadvantage is that a blank row also exists in the Table.
3. so the third solution: copy and paste all the controls of Form in the maintenance area to the same Formlayout, and set value = "# {bind. field name. inputvalue} "changed to value =" "(if it is necessary to change other attributes to" "), assuming Form B (originally called Form A), all controls in B
Unified two attributes: rendered = "#{! PageFlowScope. manageBean. flag} "disabled =" true"
In A, add rendered = "# {pageFlowScope. manageBean. flag}". In manageBean, the initial method-call method code
This. setFlag (false );
If (am. getVO1 () getEstimatedRowCount ()! = 0)
{
This. setFlag (true );
}
PS: it is particularly important that the input control points partialTriggers to the Button. I tested it. If the CommandToorbarButton. rendered attribute is not automatically refreshed, commandButton can be used to automatically refresh
,