Issue Details (XML | Word | Printable)

Key: ADFEMG-67
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jan Vervecken
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
adfemg

ADF Mobile : pageFlowScope managed-bean in bounded task-flow

Created: 26/Oct/12 08:17 PM   Updated: 27/Mar/14 04:50 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: chriscmuir and Jan Vervecken


 Description  « Hide

hi

Please consider the example application created using JDeveloper 11.1.2.3.0
at http://www.consideringred.com/files/oracle/2012/NavigationTimeMApp-v0.01.zip
and as APK at http://www.consideringred.com/files/oracle/2012/navigationtimemapp-v0.01.apk

It allows for the following scenario (sc1):

  • (sc1-a) start the app
  • (sc1-b) click the "do goSecondView using pf_TimerBean" button, which will navigate to "secondView" showing something like "no timer info yet"
  • (sc1-c) click the "do goFirstView using pf_TimerBean" button, which will navigate to "firstView" showing something like "no timer info yet"
  • (sc1-d) if you care to stop the app, try a "Force stop" on the "App info" via "Apps" in the Android settings

And also scenario (sc2):

  • (sc2-a) start the app
  • (sc2-b) click the "do goSecondView using a_TimerBean" button, which will navigate to "secondView" showing something like "timer started 621 milliseconds ago"
  • (sc2-c) click the "do goFirstView using a_TimerBean" button, which will navigate to "firstView" showing something like "timer started 537 milliseconds ago"
  • (sc2-d) if you care to stop the app, try a "Force stop" on the "App info" via "Apps" in the Android settings

The page firstView.amx has these components (and similar in secondView.amx):

<amx:outputText value="pf_TimerBean : #{pageFlowScope.pf_TimerBean.timerInfo}" id="ot2"/>
<amx:commandButton text="do goSecondView using pf_TimerBean" id="cb1" action="goSecondView"
               actionListener="#{pageFlowScope.pf_TimerBean.startTimer}"/>
<amx:outputText value="a_TimerBean : #{a_TimerBean.timerInfo}" id="ot3"/>
<amx:commandButton text="do goSecondView using a_TimerBean" id="cb2" action="goSecondView"
               actionListener="#{a_TimerBean.startTimer}"/>

It looks like the managed-bean #{pageFlowScope.pf_TimerBean} is not shared between the pages/views in the bounded task-flow.

  • (q1) Why does scenario (sc1) not behave similar to scenario (sc2) (allowing to measure time by accessing the same managed-bean instance on both pages/views)?

many thanks
Jan Vervecken



Sort Order: Ascending order - Click to sort in descending order
No changes have yet been made on this issue.