VALIDATETAG
command line keywordVALIDATETAG
specifies whether to enforce JSP tag validation and
check for items such as duplicate field identification or malformed attributes
when designing or deploying a JSP-based Web report.
The executables that can use this keyword are:
rwbuilder |
yes |
rwrun |
no |
rwclient |
no |
rwcgi |
no |
rwserver |
no |
rwservlet |
no |
rwconverter |
no |
VALIDATETAG=YES|NO
Values |
Description |
|
Enforces tag validation and checks for items such as duplicate field identification or malformed attributes. This is the default at design time, when running a JSP-based Web report from Reports Builder |
|
Turns tag validation off. This is the default at run time, when deploying a JSP-based Web report. |
This feature is useful only during the design phase, but not in the production
environment. By default, VALIDATETAG=YES
in Reports Builder
during report design, and VALIDATETAG=NO
in OracleAS Reports
Services for report deployment. To turn this option on when deploying a
report, specify VALIDATETAG=YES
in your http request (for example,
http://my.server.com/myreport.jsp?VALIDATETAG=YES
).
Using VALIDATETAG=YES
when deploying a report slows performance.
If you start Reports Builder from the command line with rwbuilder
VALIDATETAG=NO
, you run the risk of designing a report with invalid
JSP tags structure.
For more information about using VALIDATETAG
to tune the performance
of your report, see the chapter "Tuning Oracle Reports" in the
OracleAS Reports Services Publishing Reports to the Web manual, available
on the Oracle Technology
Network Oracle Reports Documentation page (http://www.oracle.com/technology/documentation/reports.html
).
Running a report from the command line
Copyright © 1984, 2005, Oracle. All rights reserved.