Which two scopes can you use to make a value in a managed bean available for at least three pages in a task (low? (Choose two.)

Question

Options

• Arequest
• Bpageflow
• Cview
• Dapplication
• Eserver

• A
  12% (6)
• B
  78% (40)
• C
  4% (2)
• E
  6% (3)

Explanation

B: Choose the pageflow scope if you want the managed bean to be accessible across the activities within a task flow. A managed bean that has a pageFlow scope shares state with pages from the task flow that access it. A managed bean that has a pageFlow scope exists for the life span of the task flow.If another task flow's page references the managed bean, the managed bean creates a separate instance of this object and adds it to the pageFlow scope of its task flow. D: The application scope lasts until the application stops. Values that you store in a managed bean with this scope are available to every session and every request that uses the application. Avoid using this scope in a task flow because it persists beyond the life span of the task flow. Incorrect Answers: A: Use request scope when the managed bean does not need to persist longer than the current C: Use this scope for managed bean objects that are needed only within the current view activity and not across view activities. It defines scope for each view port that ADF Controller manages, for example, a root browser window or an ADF region. The life span of this scope begins and ends when the current viewId of a view port changes. If you specify view, the application retains managed bean objects used on a page as long as the user continues to interact with the page. These objects are automatically released when the user leaves the page. E: There is no server scope

No community discussion yet for this question.