hi
Please consider this example application created using JDeveloper 11.1.1.3.0
http://www.consideringred.com/files/oracle/2010/MethodCallActivityParamApp-v0.01.zip
It has a some-emp-stuff-btf.xml task-flow that behaves as I would expect it to behave, and it uses the EL expression #{pageFlowScope.pEnameParam} in different places.
- (EL1) the "checkInput" Router Activity has a case expression using the EL expression #{pageFlowScope.pEnameParam} which I could select from the Expression Builder (see
MCAP-RouterActivityExpressionBuilder.png)
- (EL2) the showSomeEmps.jsff has an af:outputText with value #{pageFlowScope.pEnameParam} which I could select from the Expression Builder (see
MCAP-OutputTextValueExpressionBuilder.png)
- (EL3) the ExecuteWithParams Method Action refers to an Action Binding that has a parameter "EnameBVar" with value #{pageFlowScope.pEnameParam}, but the Expression Builder does not allow me to select this EL expression (see
MCAP-ActionBindingParameterExpressionBuilder.png)
question
- (q1) Should I be able to use the EL expression #{pageFlowScope.pEnameParam} as Action Binding prameter value expression (as in (EL3))?
- (q2) How do I determine which is "intended behaviour" (for (EL3)), design-time (not allowed) or run-time (behaves OK), so that I will not run into problems with a next release of JDeveloper (and ADF)?
many thanks
Jan Vervecken