First page Back Continue Last page Text

oracle adf workshop


Correcting Failures to Invoke Actions and Methods (continued)

To debug an invocation of a coded method for the binding container, perform the following steps:

1. In your class, set a breakpoint on the desired method.

2. In the oracle.adf.model.generic.DCGenericDataControl class, set a breakpoint on invokeMethod() to halt processing before looking into the Data window.

3. When processing pauses, step into the method to verify that instanceName in the Data window shows that the method being invoked is the intended method on the desired object.

4. Verify that args in the Data window shows the parameter value for each parameter being passed into your method is as expected.

If the debugger does not reach a breakpoint that you set on an action in the binding container, then the error is most likely a result of the way the executable’s Refresh and RefreshCondition attributes were defined. Examine the attribute definitions.

Whether the <invokeAction> executable is refreshed during the Prepare Model phase, depends on the value of Refresh and RefreshCondition (if they exist). If Refresh is set to prepareModel, or if no value is supplied (meaning it uses the default, ifneeded), then the RefreshCondition attribute value is evaluated. If no RefreshCondition value exists, the executable is invoked. If a value for RefreshCondition exists, then that value is evaluated, and if the return value of the evaluation is true, then the executable is invoked. If the value evaluates to false, the executable is not invoked. The default value always enforces execution.