X

The blog for hints & tips about Oracle Application Development Framework and Mobile Application Framework

  • ADFv
    January 16, 2011

How-to enable user session time out warning (JDev 11.1.1.4)

Frank Nimphius
Master Principal Product Manager

Oracle JDeveloper 11.1.1.4 contains a new session time-out
warning functionality.

Quoting the Oracle®
Fusion Middleware Web User Interface Developer's Guide for Oracle Application
Development Framework11g Release 1 (11.1.1.4.0) documentatiom

http://download.oracle.com/docs/cd/E17904_01/web.1111/b31973/ap_config.htm#BABFIGBA

"When a request
is sent to the server, a session timeout value is written to the page and the
session timeout warning interval is defined by the context parameter

 oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT.

The user is given the
opportunity to extend the session in a warning dialog, and a notification is
sent when the session has expired and the page is refreshed. Depending on the
application security configuration, the user may be redirected to the log in
page when the session expires.

Use the oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT
context parameter to set the number of seconds prior to the session time out
when a warning dialog is displayed. If the value of WARNING_BEFORE_TIMEOUT is
less than 120 seconds, if client state saving is used for the page, or if the
session has been invalidated, the feature is disabled. The session time-out
value it taken directly from the session.

Example A-3
shows configuration of the warning dialog to display at 120 seconds before the
time-out of the session.

Example A-3
Configuration of Session Time-out Warning

<context-param>

   <param-name>
        oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT
   </param-name>

   <param-value>120</param-value>

</context-param>

The default value of
this parameter is 120 seconds. To prevent notification of the user too
frequently when the session time-out is set too short, the actual value of WARNING_BEFORE_TIMEOUT
is determined dynamically, where the session time-out must be more than 2
minutes or the feature is disabled.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha