tell me more icon Change Persistence Using MDS

User customizations or change persistence allow end users to make changes to certain UI components at runtime to suit individual preferences (for example, which columns are visible in a table). There are two types of user customizations:

  • Those that stay in place through the length of the user's session until the user exits the application
  • Those that are permanently stored in a repository and are restored whenever the user reenters the application

In this step you are enabling user customizations across sessions using MDS as the repository.

When you enable MDS user customizations, JDeveloper adds the following context initialization parameter into web.xml, if not already added:

                               
<context-param>
  <param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name>
  <param-value>oracle.adf.view.rich.change.FilteredPersistenceChangeManager</param-value>
</context-param>
                            

The value of CHANGE_PERSISTENCE is set to oracle.adf.view.rich.change.FilteredPersistenceChangeManager for MDS change persistence or user customizations.

The following is also required in adf-config.xml for working with MDS change persistence (which JDeveloper has done for you):

                               
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
  <persistent-change-manager>
    <persistent-change-manager-class>
     oracle.adf.view.rich.change.MDSDocumentChangeManager
    </persistent-change-manager-class>
  </persistent-change-manager>
</adf-faces-config>
                            

In addition to the elements JDeveloper added for you, to use MDS change persistence, the ADF Faces components that you want to persist changes must have unique Id attribute values.

Copyright © 1997, 2009, Oracle. All rights reserved.

false ,,,,,,,,,,,,,,,