ADF Mobile : sample no Vegas

Question

hi
Please consider this tweet by Duncan Mills
" @fnimphiu so it's like Vegas - "what happens in a region - stays in a region" "
at https://twitter.com/DuncanMills/status/255318833412308992
I wonder how much this translates to bounded task-flows and using managed-beans in a bounded task-flow that are defined in a wider scope outside the bounded task-flow.
In the ADF Mobile CompGallery sample application [1] the bounded task-flow "general-taskflow" has a view configured for the page "commandButton.amx".
That "commandButton.amx" page has this button component:
<amx:commandButton id="back" action="__back" text="General">
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.text}" from="#{pageFlowScope.pText}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.rendered}" from="#{pageFlowScope.pRendered}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.icon}" from="#{pageFlowScope.pIcon}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.iconPosition}" from="#{pageFlowScope.pIconPosition}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.styleClass}" from="#{pageFlowScope.pStyleClass}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.inlineStyle}" from="#{pageFlowScope.pInlineStyle}" type="action"/>
     <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.disabled}" from="#{pageFlowScope.pDisabled}" type="action"/>
</amx:commandButton>The #{AmxProperties} managed-bean has been defined in adfc-mobile-config.xml like:
    <managed-bean id="__37">
        <managed-bean-name>AmxProperties</managed-bean-name>
        <managed-bean-class>mobile.AmxProperties</managed-bean-class>
        <managed-bean-scope>application</managed-bean-scope>
    </managed-bean>- (q1) Is using (depending on) an application-scoped managed-bean in a bounded task-flow view/page good practice (in ADF Mobile)?
- [1] http://docs.oracle.com/cd/E35521_01/doc.111230/e24475/demoapps.htm#BACGDHDJ
many thanks
Jan Vervecken

Answer 1

Hi,
First let's forget region for a sec (or a while), since ADF Mobil has no region support. :-)
Now, ADF Mobile primarily supports 3 types of scopes for managed bean: application, pageFlow, and view. The definition and scope for these scope variables are basically the same as the "big" ADF cousin, except "application" takes on a little more significance. In ADF Mobile applications, we introduced a concept called "features", where each feature can be implemented either in AMX, local HTML, or Remote HTML. To pass state between features, you would need to use application scope variables. This is how, for example, you can pass data from a Remote HTML feature into an app scope variable, and then have the AMX feature to consume it.
Otherwise, the best practice is the same - application is to share data across the entire mobile app/between features, pageFlow is for a task flow, and view is for a view.
In this case below, the intent for the property related managed beans is simply to retain property values as user select between different components (and corresponding task flows) to view how component behaves. The managed beans for DVT component data are set to be application scope, also to allow multiple DVT components and corresponding task flows to share the same data.
Thanks,
Joe Huang