Behavior in Previous Releases Obtaining the Behavior of Prior Releases in the Current Release Considerations for Template HTML Files
3.3.4.2 Behavior in Previous Releases
Release 9.0.4 and later behave the same as the current release except that a quote must be escaped 22 within the value of a runform parameter in a configuration file, and in the template HTML file. Releases before 9.0.4 did not allow URL escape sequences in runform parameter values specified in the template HTML file or the configuration file cases 1 and 2 above. In all three cases, it was difficult or impossible to specify certain special characters, notably space, quote, and apostrophe. Also, certain transformations were applied to the parameter value before passing it to runform. Most notably, if a value began and ended with an apostrophe, these were typically stripped off. However, these transformations were not well-defined, and they differed between the Web and clientserver environments.3.3.4.3 Obtaining the Behavior of Prior Releases in the Current Release
If your applications are dependent on the behavior of prior releases, you can obtain that behavior in the current release, by simply setting the value of the escapeparams variable to False in the configuration file this can be accomplished using Fusion Middleware Control. If you want to obtain the old behavior only for selected applications, you can specify different values for the escapeparams variable in different configuration sections. Applications that require the old behavior can specify a configuration section in which the escapeparams variable is set to False; applications that require or tolerate the behavior in the current release can specify a configuration section in which the escapeparams variable is set to True.3.3.4.4 Considerations for Template HTML Files
If you are creating your own template HTML files, then bear in mind the following: It is recommended that a reference to the escapeparams variable the string escapeparams, if is the HTML delimiter character appear at the beginning of the value of the serverArgs applet parameter, followed by a space. See the shipped base.htm file for an example. References to the escapeparams variable must appear nowhere else in the template HTML file. If you choose to enclose the value of the serverArgs applet parameter in apostrophes instead of quotes, then within the value of a runform parameter in your template HTML file, apostrophes must be escaped 27. Quotes do not require escape sequences. It is permissible to omit the reference to the escapeparams variable from the beginning of the value of the serverArgs applet parameter. This results in the behavior of prior releases, regardless of the value specified in the configuration file for the escapeparams variable.3.3.4.5 Considerations for Static HTML Pages
Parts
» Oracle Fusion Middleware Online Documentation Library
» Oracle Forms Developer Oracle Forms Services
» Oracle Database Oracle WebLogic Server Oracle Fusion Middleware
» Forms Listener Servlet Forms Runtime Process
» About Installing or Upgrading Oracle Forms Oracle Forms Services in Action
» default.env Oracle Forms Configuration Files
» Forms Java EE Application Deployment Descriptors Standard Fonts and Icons File baseHTML Files
» Deploying Your Application Application Deployment
» Default Behavior in the Current Release
» Accessing Forms Services with Fusion Middleware Control
» Common Tasks in the Web Configuration Page
» Managing Parameters Configuring Forms Services
» Basic Configuration Parameters Single Sign-On Configuration Parameters
» Trace Configuration Parameters Plug-in Configuration Parameters HTML Page Configuration Parameters
» Applet Configuration Parameters Forms Configuration Parameters
» Advanced Configuration Parameters Forms Configuration Parameters
» Managing Environment Configuration Files Configuring Environment Variables
» Managing User Sessions Oracle Fusion Middleware Online Documentation Library
» Securing the Oracle Forms Test Form
» Managing Registry.dat with Fusion Middleware Control Managing Application Fonts
» Creating a Jar File for Images Using Files Within the Jar File
» DocumentBase codebase Search Path for Icons and Images
» Example change: Swapping Enter and Execute Mappings Exceptions Special Key Mappings
» About the Oracle WebLogic Managed Server
» Prerequisite Steps Custom Deployment of Forms Java EE Application
» Override the Default Servlet Alias and the Context Root
» Expanding Forms Managed Server Clusters Registering Forms Java EE Applications
» Modification of Forms J2EE Application Deployment Descriptors
» Load Balancing Oracle WebLogic Server
» Enabling SSL with a Load Balancing Router
» Integrating JavaScript and Oracle Forms Configuration of formsweb.cfg
» Configuration of Environment Variables About Oracle Forms and Server Events
» About the When-Event-Raised Trigger About Trigger Definition Level and Scope
» Creating Events Subscribing to Events Publishing Database Events
» About Synchronous Communication About Asynchronous Communication
» ssoErrorURL ssoCancelUrl Enabling OracleAS Single Sign-On for an Application
» Proxy User Overview Enabling and Configuring Proxy Users
» Enabling Proxy User Connections
» Enabling SSO in formsweb.cfg Accessing the Forms Application Changes in Forms Built-ins
» OracleAS Single Sign-On Components Used By Oracle Forms Configuring Oracle Internet Directory
» About Multiple JVM Controllers JVM Pooling Usage Examples
» Re-importing Your Java Code About Sharing Static Variables Across Multiple JVMs
» JVM Controller Command Examples
» Click Delete. Deleting a Named Configuration
» Common Tasks in the JVM Configuration Page Managing Parameters
» Forms Configuration File Settings Startup Example
» Overview of JVM Configuration Integrating Forms and Reports JVM Pooling Error Messages
» Configuring Forms Trace Specifying URL Parameter Options
» Starting and Stopping Forms Trace
» Specifying Logging Specifying Logging Levels Using Fusion Middleware Control
» none session sessionperf perf
» debug Example Output for Each Level of Servlet Logging
» Upgrading Common Gateway Interface CGI to the Oracle Forms Servlet
» Upgrading the Forms 6i Listener to the Forms Listener Servlet
» Upgrading the Forms Listener Servlet Architecture to Oracle Forms Services
» Creating Forms Listener Servlet Alias Names Accessing the Listener Servlet Administration Page
» Configuring Prestart Parameters Forms Services Web Runtime Pooling
» Using Java Files Using Oracles Java Plug-in Using Caching
Show more