The process of saving application state to a secondary medium (in the case of OA Framework,
database tables) is called passivation.
The process of saving object state to a secondary medium. This is similar to Java I/O serialization, but passivation is a more generic concept. Serialization is one way to save data.
Consider a multi-page purchase order creation flow where the user describes the order in the first page, enters one or more line items in the second page, and reviews the order before submitting it in the third page. The purchase order data (its state) must remain intact between each of the browser requests for the transaction to be completed successfully.
NOTE:-->Set the Retention Level for root application modules only. Do not set it for nested application modules as their passivation behavior is determined by the root application module's configuration. For example, do not set this property for application modules associated with LOVs and attachment pages as these application modules are nested under the main page's root application module. However, because they are passivated with the root application module, nested application modules must observe all the state management coding standards.
Set each root application module's Retention Level to MANAGE_STATE.
Reason why---> This allows OA Framework to recover connections and memory under resource load, support session failover, and other pending features such as Save For Later and JVM failover.
Source: https://forums.oracle.com/forums/thread.jspa?threadID=859349
database tables) is called passivation.
The process of saving object state to a secondary medium. This is similar to Java I/O serialization, but passivation is a more generic concept. Serialization is one way to save data.
Consider a multi-page purchase order creation flow where the user describes the order in the first page, enters one or more line items in the second page, and reviews the order before submitting it in the third page. The purchase order data (its state) must remain intact between each of the browser requests for the transaction to be completed successfully.
NOTE:-->Set the Retention Level for root application modules only. Do not set it for nested application modules as their passivation behavior is determined by the root application module's configuration. For example, do not set this property for application modules associated with LOVs and attachment pages as these application modules are nested under the main page's root application module. However, because they are passivated with the root application module, nested application modules must observe all the state management coding standards.
Set each root application module's Retention Level to MANAGE_STATE.
Reason why---> This allows OA Framework to recover connections and memory under resource load, support session failover, and other pending features such as Save For Later and JVM failover.
Source: https://forums.oracle.com/forums/thread.jspa?threadID=859349
