Oracle Application Server Containers for J2EE Support for JavaServer Pages Developer's Guide 10g (9.0.4) Part Number B10320-01 |
|
This chapter discusses operation of the OC4J JSP translator, then discusses the ojspc
utility and situations where pretranslation is useful, followed by general discussion of a number of additional JSP deployment considerations.
The following sections are included:
JSP translators generate standard Java code for a JSP page implementation class. This class is essentially a servlet class wrapped with features for JSP functionality.
The following sections discuss general functionality of the JSP translator, focusing on its behavior in on-demand translation scenarios such as in OC4J in the Oracle Application Server:
This section discusses general features of the page implementation class code that is produced by the JSP translator in translating JSP source (typically .jsp
and .sqljsp
files).
When the JSP translator generates servlet code in the page implementation class, it automatically handles some of the standard programming overhead. For both the on-demand translation model and the pretranslation model, generated code automatically includes the following features:
javax.servlet.jsp.HttpJspPage
interface, which extends the more generic javax.servlet.jsp.JspPage
interface, which in turn extends the javax.servlet.Servlet
interface.
_jspService()
method specified by the HttpJspPage
interface. This method, often referred to as the "service" method, is the central method of the page implementation class. Code from any Java scriptlets, expressions, and JSP tags in the JSP page is incorporated into this method implementation.
session="false"
in a page
directive.
For introductory information about key JSP and servlet classes and interfaces, see Appendix A, "Servlet and JSP Technical Background".
The service method, _jspService()
, of the page implementation class includes print statements--out.print()
or equivalent calls on the implicit out
object--to print any static text in the JSP page. The JSP translator places the static text itself in a series of member variables in the page implementation class. The service method out.print()
statements reference these member variables to print the text.
Notes:
|
The JSP translator follows a consistent set of conventions in naming output classes, packages, files, and directories. However, this set of conventions and other implementation details may change from release to release.
One fact that is not subject to change, however, is that the base name of a JSP page will be included intact in output class and file names as long as it does not include special characters. For example, translating MyPage123.jsp
will always result in the string "MyPage123" being part of the page implementation class name, Java source file name, and class file name.
In Oracle Application Server 10g (9.0.4), the base name is preceded by an underscore ("_"). Translating MyPage123.jsp
results in the page implementation class _MyPage123
in the source file _MyPage123.java
, which is compiled into _MyPage123.class
.
Similarly, where path names are used in creating Java package names, each component of the path is preceded by an underscore. Translating /jspdir/myapp/MyPage123.jsp
, for example, results in class _MyPage123
being in the following package:
_jspdir._myapp
The package name is used in creating directories for output .java
and .class
files, so the underscores are also evident in output directory names. For example, in translating a JSP page in a directory such as webapp/test
, the JSP translator by default will create a directory such as webappdeployment/_pages/_test
for the page implementation class source. All output directories are created under the standard _pages
directory, as described in "Generated Files and Locations".
If you include special characters in a JSP page name or path name, the JSP translator takes steps to ensure that no illegal Java characters appear in the output class, package, and file names. For example, translating My-name_foo12.jsp
results in _My_2d_name__foo12
being the class name, in source file _My_2d_name__foo12.java
. The hyphen is converted to a string of alpha-numeric characters. (An extra underscore is also inserted before "foo12
".) In this case, you can only be assured that alphanumeric components of the JSP page name will be included intact in the output class and file names. For example, you could search for "My
", "name
", or "foo12
".
These conventions are demonstrated in examples provided later in this chapter.
Although the JSP specification defines a uniform process for parsing and translating JSP text, it does not describe how the generated classes should be named. That is up to each JSP implementation.
This section describes how the OC4J JSP translator creates package and class names when it generates code during translation.
Note: For information about general conventions that the OC4J JSP translator uses in naming output classes, packages, and files, see "General Conventions for Output Names". |
In an on-demand translation scenario, the URL path that is specified when the user requests a JSP page--specifically, the path relative to the document root or application root--determines the package name for the generated page implementation class. Each directory in the URL path represents a level of the package hierarchy.
It is important to note, however, that generated package names are always lowercase, regardless of the case in the URL.
Consider the following URL as an example:
http://host:port/HR/expenses/login.jsp
In the current OC4J JSP implementation, this results in the following package specification in the generated code:
package _hr._expenses;
(Implementation details are subject to change in future releases.)
No package name is generated if the JSP page is at the application root directory, where the URL is as follows:
http://host:port/login.jsp
The base name of the .jsp
file (or .sqljsp
file) determines the class name in the generated code.
Consider the following URL example:
http://host:port/HR/expenses/UserLogin.jsp
In the current OC4J JSP implementation, this yields the following class name in the generated code:
public class _UserLogin extends ...
(Implementation details are subject to change in future releases.)
Be aware that the case (lowercase/uppercase) that users specify in the URL must match the case of the actual .jsp
or .sqljsp
file name. For example, they can specify UserLogin.jsp
if that is the actual file name, or userlogin.jsp
if that is the actual file name, but not userlogin.jsp
if UserLogin.jsp
is the actual file name.
Currently, the translator determines the case of the class name according to the case of the file name. For example:
UserLogin.jsp
results in the class _UserLogin
.
Userlogin.jsp
results in the class _Userlogin
.
userlogin.jsp
results in the class _userlogin
.
If you care about the case of the class name, then you must name the .jsp
file or .sqljsp
file accordingly. However, because the page implementation class is invisible to the end user, this is usually not a concern.
For on-demand translation scenarios, this section describes files that are generated by the JSP translator and where they are placed. (For pretranslation scenarios, ojspc
places files differently and has its own set of relevant options. See "Summary of ojspc Output Files, Locations, and Related Options".)
Wherever JSP configuration parameters are mentioned, see "JSP Configuration Parameters" for more information.
Note: For information about general conventions used in naming output classes, packages, and files, see "General Conventions for Output Names". |
This section considers both regular JSP pages (.jsp
files) and SQLJ JSP pages (.sqljsp
files or files with language="sqlj"
in a page
directive) in listing files that are generated by the JSP translator. For the file name examples, presume a file Foo.jsp
or Foo.sqljsp
is being translated.
Source files:
.sqlj
file (for example, _Foo.sqlj
) is produced by the OC4J JSP translator if the page is a SQLJ JSP page.
.java
file (for example, _Foo.java
) is produced for the page implementation class. It is produced either directly by the JSP translator from the.jsp
file, or by the SQLJ translator from the.sqlj
file if the page is a SQLJ JSP page. The currently installed Oracle SQLJ translator is used by default, but you can specify an alternative translator by using the sqljcmd
JSP configuration parameter.
Binary files:
.ser
Java resource files, but they will be .class
files if you enable the SQLJ -ser2class
flag through the sqljcmd
configuration parameter. The resource file or .class
file has "Foo" as part of its name. (The default SQLJ code generation is -codegen=oracle
, for Oracle-specific code. No profiles are generated for Oracle-specific code. For ISO code, use -codegen=iso
.)
.class
file is produced by the Java compiler for the page implementation class. The Java compiler is the JDK javac
by default, but you can specify an alternative compiler using the JSP javaccmd
configuration parameter.
.res
Java resource file (for example, _Foo.res
) is optionally produced for the static page content if the external_resource
JSP configuration parameter is enabled.
The JSP translator places generated output files under a _pages
directory that is created under the JSP cache directory, which is specified in the jsp-cache-directory
attribute of the <orion-web-app>
element in either the global-web-application.xml
file or the application orion-web.xml
file. Here is the general base location if you assume the default "./persistence
" value of jsp-cache-directory
:
ORACLE_HOME/j2ee/home/app-deployment/app-name/web-app-name/persistence/_pages/...
In OC4J standalone, here is the location relative to where OC4J is installed:
j2ee/home/app-deployment/app-name/web-app-name/persistence/_pages/...
Note the following, and refer to "Key OC4J Configuration Files" for related information about the noted configuration files:
app-deployment
directory is the OC4J deployment directory specified in the OC4J server.xml
file. (In OC4J standalone, this is typically the application-deployments
directory.)
app-name
is the application name, according to an <application>
element in server.xml
.
web-app-name
is the corresponding "Web application name", mapped to the application name in a <web-app>
element in the OC4J Web site XML file (typically default-web-site.xml
file in Oracle Application Server or http-web-site.xml
in OC4J standalone).
The path under the _pages
directory depends on the path of the .jsp
file under the application root directory.
As an example, in OC4J standalone, consider the page welcome.jsp
in the examples/jsp
subdirectory under the OC4J standalone default Web application directory. The path to this page would be as follows, relative to where OC4J is installed:
j2ee/home/default-web-app/examples/jsp/welcome.jsp
Assuming the default application deployment directory, the JSP translator would place the output files ( _welcome.java
and _welcome.class
) in the following directory:
j2ee/home/application-deployments/default/defaultWebApp/persistence/_pages/_examples/_jsp
Because the .jsp
source file is in the examples/jsp
subdirectory under the application root directory, the JSP translator generates _examples._jsp
as the package name and places the output files into an _examples/_jsp
subdirectory under the _pages
directory.
Note the following for OC4J standalone:
application-deployments
directory is the OC4J default deployment directory.
default
is the OC4J default application name and defaultWebApp
is the default Web application name, both used for JSP pages placed in the default-web-app
directory.
The OC4J JSP container provides a feature called global includes. You can use this feature to specify one or more files to statically include into JSP pages in or under a specified directory, through virtual JSP include
directives. During translation, the JSP container looks for a configuration file, /WEB-INF/ojsp-global-include.xml
, that specifies the included files and the directories for the pages.
This enhancement is particularly convenient for migrating applications that used globals.jsa
or translate_params
functionality in previous Oracle JSP releases.
Globally included files can be used for the following, for example:
globals.jsa
)
translate_params
(typically for a JServ environment)
The ojsp-global-include.xml
file specifies the names of files to include, whether they should be included at the tops or bottoms of JSP pages, and the locations of JSP pages to which the global includes should apply. This section describes the elements of ojsp-global-include.xml
.
This is the root element of the ojsp-global-include.xml
file. It has no attributes.
Subelement of <ojsp-global-include>
:
<include>
Use the <include>
subelement of <ojsp-global-include>
to specify a file to be included and whether it should be included at the top or bottom of JSP pages.
Subelement of <include>
:
<into>
Attributes of <include>
:
file
: Specify the file to be included, such as "/header.html"
or "/WEB-INF/globalbeandeclarations.jsph"
. The file name setting must start with a slash ("/
"). In other words, it must be application-relative, not page-relative.
position
: Specify whether the file is to be included at the top or bottom of JSP pages. Supported values are "top
" (default) and "bottom
".
Use this subelement of <include>
to specify a location (a directory, and possibly subdirectories) of JSP pages into which the specified file is to be included. This element has no subelements.
Attributes of <into>
:
directory
: Specify a directory. Any JSP pages in this directory, and optionally its subdirectories, will statically include the file specified in the file
attribute of the <include>
element. The directory
setting must start with a slash ("/
"), such as "/dir1"
. The setting can also include a slash after the directory name, such as "/dir1/"
, or a slash will be appended internally during translation.
subdir
: Use this to specify whether JSP pages in all subdirectories of the directory
should also have the file statically include. Supported values are "true
" (default) and "false
".
This section provides examples of global includes.
Assume the following ojsp-global-include.xml
file:
<?xml version="1.0" standalone='yes'?> <!DOCTYPE ojsp-global-include SYSTEM 'ojsp-global-include.dtd'> <ojsp-global-include> <include file="/header.html"> <into directory="/dir1" /> </include> <include file="/footer1.html" position="bottom"> <into directory="/dir1" subdir="false" /> <into directory="/dir1/part1/" subdir="false" /> </include> <include file="/footer2.html" position="bottom"> <into directory="/dir1/part2/" subdir="false" /> </include> </ojsp-global-include>
This example accomplishes three objectives:
header.html
file is included at the top of any JSP page in or under the dir1
directory. The result would be the same as if each .jsp
file in or under this directory had the following include
directive at the top of the page:
<%@ include file="/header.html" %>
footer1.html
file is included at the bottom of any JSP page in the dir1
directory or its part1
subdirectory. The result would be the same as if each .jsp
file in those directories had the following include
directive at the bottom of the page:
<%@ include file="/footer1.html" %>
footer2.html
file is included at the bottom of any JSP page in the part2
subdirectory of dir1
. The result would be the same as if each .jsp
file in that directory had the following include
directive at the bottom of the page:
<%@ include file="/footer2.html" %>
Assume the following ojsp-global-include.xml
file:
<?xml version="1.0" standalone='yes'?> <!DOCTYPE ojsp-global-include SYSTEM 'ojsp-global-include.dtd'> <ojsp-global-include> <include file="/WEB-INF/nls/params.jsf"> <into directory="/" /> </include> </ojsp-global-include>
And assume params.jsf
contains the following:
<% request.setCharacterEncoding(response.getCharacterEncoding()); %>
The params.jsf
file (essentially, the setCharacterEncoding()
method call) is included at the top of any JSP page in or under the application root directory. In other words, it is included in any JSP page in the application. The result would be the same as if each .jsp
file in or under this directory had the following include
directive at the top of the page:
<%@ include file="/WEB-INF/nls/parms.jsf" %>
Also see "Migration from translate_params".
The ojspc
utility is provided with OC4J for pretranslation of JSP pages. For consideration of pretranslation scenarios, see "JSP Pretranslation" and "Deployment of Binary Files Only".
The following sections discuss ojspc
functionality:
For a simple JSP (not SQLJ JSP) page, default functionality for ojspc
is as follows:
.jsp
), either directly as an argument or from an archive file taken as an argument.
.java
file.
.java
file, producing a .class
file for the page implementation class.
Following is the default ojspc
functionality for a SQLJ JSP page:
.sqljsp
file or a JSP file with language="sqlj"
in a page
directive), either directly as an argument or from an archive file taken as an argument.
.sqlj
file for the page implementation class.
.sqlj
file. This produces a .java
file for the page implementation class. Also, for ISO code generation, translation produces a SQLJ profile file that is, by default, a .ser
Java resource file.
For information about SQLJ profiles and Oracle-specific code generation, see the Oracle9i SQLJ Developer's Guide and Reference.
.java
file, producing a .class
file for the page implementation class.
Under some circumstances (as is noted in the -extres
option description later in this chapter), ojspc
options direct the JSP translator to produce a .res
Java resource file for static page content, instead of putting this content into the page implementation class.
Because ojspc
invokes the JSP translator, ojspc
output conventions are the same as for the translator in general, as applicable. For general information about JSP translator output, including generated code features, general conventions for output names, generated package and class names, and generated files and locations, see "Functionality of the JSP Translator".
Prior to Oracle9iAS Release 2 (9.0.3), ojspc
accepted only JSP files (or SQLJ JSP files) for translation. Now, however, it can also accept archive files--JAR, WAR, EAR, or ZIP files--for batch pretranslation.
When the name of an archive file appears on the ojspc
command line, ojspc
by default executes the following steps:
.jsp
, .sqljsp
, .sqlj
, and .java
files in the archive file.
.class
files and any Java resource files into a nested JAR file inside the archive file, and discards .java
and .sqlj
files that were created in the process. The .class
and resource files in the nested JAR file have directory paths such that upon extraction, they will be located in the same directory as would be the case if the original JSP files were translated after extraction.
By default, the mechanics are that the original archive file is extracted into a temporary storage area, a temporary archive file is created, contents of the original archive file are copied into the temporary file, output .class
and resource files from pretranslation are added to a nested JAR file within the temporary file, the original archive file is deleted, and the temporary file is given the name of the original file. The original archive file is extracted in its entirety to ensure successful compilation of the translated pages. Alternatively, you have the option of specifying a new output file name, which will preserve the original archive file.
The nested JAR file is in the _pages
directory of the resulting archive file. Its name includes the base name of the resulting archive file (either the original archive file name or a name according to the ojspc
-output
option) and has the .jar
extension. In the OC4J 9.0.4 implementation, assuming an archive output file name of myarch.war
, for example, the nested JAR file name would be __oracle_jsp_myarch.jar
. Implementation details might change in future releases, but the base name of the archive file will always be included in the nested JAR file name.
File paths within the nested JAR file are according to Java package names and according to specified file paths of JSP include and forward statements, as applicable and as one would expect.
There are ojspc
settings for additional functionality, as follows:
-batchMask
option to specify file name extensions for pretranslation and compilation. Whatever you specify is used instead of the defaults (*.jsp
, *.sqljsp
, *.sqlj
, and *.java
).
-output
option to specify a new archive file name. By default, ojspc
updates the original archive file, adding output .class
files and any resource files (and possibly deleting processed source files, according to the -deleteSource
option). If you want to be sure that the original archive file is unaltered, then enable the -output
option. In this case, all contents of the original archive file are copied into the specified output archive file, then the specified output archive file is updated instead of the original file. The original archive file is unaltered, and you would use the new file instead of the original file for deployment.
-deleteSource
option if you do not want processed source files to appear in the resulting archive file. If you do not also use the -output
option, this effectively means that all processed source files are removed from the original archive file after processing. If you do not use the -batchMask
option, this consists of all .jsp
, .sqljsp
, .sqlj
, and .java
files. Otherwise, this consists of all files specified in the -batchMask
setting.
For examples of these options, see the descriptions of those options under "Option Descriptions for ojspc".
Table 7-1 summarizes the options supported by the ojspc
pretranslation utility. These options are further discussed in "Option Descriptions for ojspc".
The second column notes comparable or related JSP configuration parameters for on-demand translation environments, such as OC4J.
Note:
For a JServ environment, use the |
Following is the general ojspc
command-line syntax (where %
is the system prompt):
% ojspc [option_settings] file_list
The file list can include JSP files (including SQLJ JSP files) and other source files (.sqlj
and .java
), or archive files (JAR, WAR, EAR, or ZIP files).
Be aware of the following syntax notes:
page
directive settings.
-extres
, not -extres true
.
Here are two examples:
% ojspc -dir /myapp/mybindir -srcdir /myapp/mysrcdir -extres MyPage.sqljsp MyPage2.jsp % ojspc -deleteSource myapp.war
This section describes the ojspc
options in more detail.
(fully qualified path; ojspc
default: empty)
Use this option to specify additional classpath entries for javac
to use when compiling generated page implementation class source. Otherwise, javac
uses only the system classpath.
(fully qualified path; ojspc
default: current directory)
Use this option to specify an application root directory. The default is your current directory when you ran ojspc
.
The specified application root directory path is used as follows:
include
directives in the page being translated
The specified directory path is prepended to any application-relative (context-relative) paths in the include
directives of the translated page.
The package will be based on the location of the file being translated relative to the application root directory. The package, in turn, determines the placement of output files. (See "Summary of ojspc Output Files, Locations, and Related Options".)
This option is necessary, for example, so that included files can still be found if you run ojspc
from some other directory.
Consider the following example.
/abc/def/ghi/test.jsp
ojspc
from the current directory, /abc
, as follows (where %
is a UNIX prompt):
% cd /abc % ojspc def/ghi/test.jsp
test.jsp
page has the following include
directive:
<%@ include file="/test2.jsp" %>
test2.jsp
page is in the /abc
directory, as follows:
/abc/test2.jsp
This example requires no -appRoot
setting because the default application root setting is the current directory, which is the /abc
directory. The include
directive uses the application-relative /test2.jsp
syntax (note the beginning "/
"), so the included page will be found as /abc/test2.jsp
.
The package in this case is _def._ghi
, based on the location of test.jsp
relative to the current directory when you ran ojspc
. (The current directory is the default application root.) Output files are placed accordingly.
If, however, you run ojspc
from some other directory, suppose /home/mydir
, then you would need an -appRoot
setting as in the following example:
% cd /home/mydir % ojspc -appRoot /abc /abc/def/ghi/test.jsp
The package is still _def._ghi
, based on the location of test.jsp
relative to the specified application root directory.
(file masks to batch-process in archive; ojspc
default: see description)
For batch pretranslation, you can use this option to specify source files to process in an archive file. By default, all .jsp
, .sqljsp
, .sqlj
, and .java
files are processed. File masks specified through the -batchMask
option are used instead of (not in addition to) these defaults.
Place quotes around the list of file masks and use commas or semicolons as delimiters within the list. White space before or after a file mask is ignored. You can include directories in the mask.
Beginning with the OC4J 9.0.4 implementation, the -batchMask
implementation includes complete support for standard wildcard pattern-matching.
Given the default setting, the following two examples are equivalent:
% ojspc myapp.war % ojspc -batchMask "*.jsp,*.sqljsp,*.sqlj,*.java" myapp.war
This next example drops processing for .java
and .sqlj
files while adding processing for .jspf
and .jsph
files:
% ojspc -batchMask "*.jspf,*.jsph,*.jsp,*.sqljsp" myapp.war
The following example does not process .sqljsp
, .sqlj
, or .java
files, and only processes .jsp
files whose names start with "abc" and who are in subdirectories under the top level of the archive file:
% ojspc -batchMask "*/abc*.jsp" myapp.zip
The following example is the same as the preceding example, but also processes .jsp
files whose names start with "abc" in the top level of the archive file:
% ojspc -batchMask "abc*.jsp, */abc*.jsp" myapp.jar
This final example specifically processes the file a.jspc
, as well as any .jsp
files that start with "My" and are in a directory that is a subdirectory of mydir/subdir
and matches the pattern "t?st" (any character as the second character, such as "test", "tast", or "tust"):
% ojspc -batchMask "mydir/subdir/t?st/My*.jsp, a.jspc" myapp.ear
(boolean; ojspc
default: false
)
Enabling this flag instructs ojspc
to generate a line map to the original JSP file for debugging. Otherwise, line-mapping will be to the generated page implementation class.
This flag is useful for source-level JSP debugging, such as when you use Oracle JDeveloper.
(boolean; ojspc
default: false
)
For batch pretranslation, enable this flag if you do not want processed source files to appear in the resulting archive file. This is .jsp
, .sqljsp
, .sqlj
, and .java
files by default, or else only the files that match the file mask in the -batchMask
option. Generated .java
and .sqlj
files are also discarded, as usual.
If you do not use the -output
option, then the contents of the original archive file are overwritten to remove any processed source files after processing. If you do use the -output
option, then processed source files will not be copied to the specified output archive file. (The original archive file is unaltered.)
Notes:
|
(fully qualified path; ojspc
default: current directory)
Use this option to specify a base directory for ojspc
placement of generated binary files--.class
files and Java resource files. (The .res
files produced for static content by the -extres
option are Java resource files, as are .ser
profile files produced by the SQLJ translator for SQLJ JSP pages with SQLJ ISO code generation.) As a shortcut, -d
is also accepted.
The specified path is taken as a file system path (not an application-relative or page-relative path), and the directory must already exist.
Subdirectories under the specified directory are created automatically, as appropriate, depending on the package. See "Summary of ojspc Output Files, Locations, and Related Options" for more information.
The default is to use the current directory (your current directory when you executed ojspc
).
It is recommended that you use this option to place generated binary files into a clean directory so that you easily know what files have been produced.
(fully qualified Java class name; ojspc
default: empty)
Use this option to specify a Java class that the generated page implementation class will extend.
(import list; ojspc
default: empty)
As described in "Default Package Imports", the OC4J JSP container has a smaller default list of packages that are imported into each JSP page than was the case prior to Oracle9iAS Release 2 (9.0.3). This is in accordance with the JSP specification. You can avoid updating your code, however, by specifying package names or fully qualified class names for any additional imports through the -extraImports
option. Be aware that the names must be in quotes, and either comma-delimited or semicolon-delimited, as in the following example:
% ojspc -extraImports "java.util.*,java.io.*" foo.jsp
Notes:
|
(boolean; ojspc
default: false
)
Enabling this flag instructs ojspc
to place static content of the page into a Java resource file instead of into the service method of the generated page implementation class.
The resource file name is based on the JSP page name. In the current OC4J JSP implementation, it will be the same core name as the JSP name (unless special characters are included in the JSP name), but with an underscore ("_") prefix and .res
suffix. Translation of MyPage.jsp
, for example, would create _MyPage.res
in addition to normal output. The exact implementation for name generation might change in future releases, however.
The resource file is placed in the same directory as output .class
files.
If there is a lot of static content in a page, this technique will speed translation and might speed execution of the page. For more information, see "Workarounds for Large Static Content or Significant Tag Library Usage".
(boolean; ojspc
default: false
)
Enabling this flag avoids translation errors in JSP 1.2 (or higher) if you have duplicate settings for the same directive attribute within a single JSP translation unit (a JSP page plus anything it includes through include
directives).
The JSP specification directs that a JSP container must verify that directive attributes, with the exception of the page
directive import
attribute, are not set more than once each within a single JSP translation unit. See "Duplicate Settings of Page Directive Attributes Are Disallowed" for more information.
The JSP 1.1 specification did not specify such a limitation. OC4J offers the -forgiveDupDirAttr
option for backward compatibility.
(boolean; ojspc
default: false
)
Use this option to have ojspc
display usage information and then exit. As a shortcut, -h
is also accepted.
(fully qualified Java interface name; ojspc
default: empty)
Use this option to specify a Java interface that the generated page implementation class will implement.
(boolean; ojspc
default: false
)
Enabling this flag directs ojspc
to not compile the generated page implementation class Java source. This is in case you want to compile it later for some reason, such as with an alternative Java compiler.
(boolean; ojspc
default: false
)
Enable this flag if you do not want XML validation of tag library descriptor (TLD) files of the application. By default, validation of TLD files is performed.
See "Overview of TLD File Validation and Features" for related information.
(boolean; ojspc
default: false
)
This is for backward compatibility with Oracle JSP versions prior to Oracle9iAS Release 2, for functionality of include
directives. If you enable this flag, page locations in nested include
directives are relative to the top-level page. Otherwise, page locations are relative to the immediate parent page, which complies with the JSP specification.
(archive file name; ojspc
default: none)
For batch pretranslation, use the -output
option if you want to specify a new archive file for output instead of updating the original archive file. In this case, all contents of the original archive file are copied into the specified archive file, then the output .class
files and any resource files from pretranslation are placed into a nested JAR file within the specified file (and source files are deleted from the specified file if -deleteSource
is enabled). The original archive file is unaltered and you would use the new file instead of the original file for deployment. (See "Overview of ojspc Batch Pretranslation" for information about the nested JAR file.)
Without the -output
option, the original archive file is updated; no new archive file is created.
Here is an example of -output
usage:
% ojspc -output myappout.war myapp.war
(fully qualified package name; ojspc
default: per .jsp
file location)
Use this option to specify a package name for the generated page implementation class, using Java "dot" syntax.
Without setting this option, the package name is determined according to the location of the .jsp
file relative to your current directory when you ran ojspc
.
Consider an example where you run ojspc
from the /myapproot
directory, while the .jsp
file is in the /myapproot/src/jspsrc
directory (where %
is a UNIX prompt):
% cd /myapproot % ojspc -packageName myroot.mypackage src/jspsrc/Foo.jsp
This results in myroot.mypackage
being used as the package name.
If this example did not use the -packageName
option, the JSP translator (in its current implementation) would use _src._jspsrc
as the package name by default. (Be aware that such implementation details are subject to change in future releases.)
(boolean; ojspc
default: false
)
The Oracle JSP implementation reduces the size of generated code for custom tag usage, but enabling this flag results in even further size reduction. There might be performance consequences regarding tag handler reuse, however. See "Tag Handler Code Generation".
(boolean; ojspc
default: false
)
Enabling this flag allows request-time JavaBean introspection whenever compile-time introspection is not possible. When compile-time introspection is possible and succeeds, however, there is no request-time introspection regardless of the setting of this flag.
As a sample scenario for request-time introspection, assume a tag handler returns a generic java.lang.Object
instance in the VariableInfo
instance of the tag-extra-info class during translation and compilation, but actually generates more specific objects during request-time (runtime). In this case, if -reqTimeIntrospection
is enabled, the JSP container will delay introspection until request-time. (See "Scripting Variables, Declarations, and Tag-Extra-Info Classes" for information about use of VariableInfo
.)
An additional effect of this flag is to allow a bean to be declared twice, such as in different branches of an if..then..else
loop. Consider the example that follows. Without -reqTimeIntrospection
being enabled, this code would cause a parse exception. With it enabled, the code will work without error:
<% if (cond) { %> <jsp:useBean id="foo" class="pkgA.Foo1" /> <% } else { %> <jsp:useBean id="foo" class="pkgA.Foo2" /> <% } %>
(-S
followed by SQLJ option setting; ojspc
default: empty)
For SQLJ JSP pages, use the ojspc
-S
option to pass an Oracle SQLJ option to the SQLJ translator. You can use multiple occurrences of -S
, where each specifies one SQLJ option setting.
Unlike when you run the SQLJ translator directly, use a space between a SQLJ option and its value (for consistency with other ojspc
options).
For example (where %
is a UNIX prompt):
% ojspc -S-codegen iso -dir /myapproot/mybindir MyPage.jsp
This directs SQLJ to generate ISO standard code instead of the default Oracle-specific code.
Here is another example:
% ojspc -S-codegen iso -S-ser2class true -dir /myapproot/mybindir MyPage.jsp
This again directs SQLJ to generate ISO standard code and also enables the -ser2class
option in order to convert the profile to a .class
file.
Note the following for particular Oracle SQLJ options:
-encoding
option; instead, use the contentType
or pageEncoding
attribute in a page
directive in the JSP page.
-classpath
option if you use the ojspc -addclasspath
option.
-compile
option if you use the ojspc -noCompile
option.
-d
option if you use the ojspc
-dir
option.
-dir
option if you use the ojspc -srcdir
option.
For information about Oracle SQLJ translator options, see the Oracle9i SQLJ Developer's Guide and Reference.
(fully qualified path; ojspc
default: current directory)
Use this option to specify a base directory location for ojspc
placement of generated source files--.sqlj
files (for SQLJ JSP pages) and .java
files.
The specified path is taken simply as a file system path, not an application-relative or page-relative path. The directory must already exist.
Subdirectories under the specified directory are created automatically, as appropriate, depending on the package. See "Summary of ojspc Output Files, Locations, and Related Options" for more information.
The default is to use the current directory (your current directory when you executed ojspc
).
It is recommended that you use this option to place generated source files into a clean directory so that you conveniently know what files have been produced.
(boolean; ojspc
default: false
)
Enabling this flag directs the JSP translator to generate static text in JSP pages as characters instead of bytes. The default setting is false
, which improves performance in outputting static text blocks.
Enable this flag if your application requires the ability to change the character encoding dynamically during runtime, such as in the following example:
<% response.setContentType("text/html; charset=UTF-8"); %>
(mode for tag handler reuse; ojspc
default: runtime
)
Use this option to specify the mode of tag handler reuse (tag handler instance pooling), as follows:
none
to disable tag handler reuse. You can override this in any particular JSP page by setting the JSP page context attribute oracle.jsp.tags.reuse
to a value of true
.
runtime
to enable the runtime model of tag handler reuse. You can override this in any particular JSP page by setting the JSP page context attribute oracle.jsp.tags.reuse
to a value of false
.
compiletime
to enable the compile-time model of tag handler reuse in its basic mode.
compiletime_with_release
to enable the compile-time model of tag handler reuse in its "with release" mode, where the tag handler release()
method is called between usages of a given tag handler within a given page.
See "Disabling or Enabling Runtime or Compile-Time Tag Handler Reuse" for more information about tag handler reuse.
(boolean; ojspc
default: false
)
Enabling this flag directs ojspc
to report its translation steps as it executes.
The following example shows -verbose
output for the translation of myerror.jsp
. (In this example, ojspc
is run from the directory where myerror.jsp
is located; assume %
is a UNIX prompt.)
% ojspc -verbose myerror.jsp Translating file: myerror.jsp 1 JSP files translated successfully. Compiling Java file: ./_myerror.java
(boolean; ojspc
default: false
)
Use this option to have ojspc
display the JSP version number and then exit.
(boolean; ojspc
default: false
)
Enable this flag if you want XML validation of the application web.xml
file. Because the Tomcat JSP reference implementation does not perform XML validation, this flag is disabled by default.
By default, ojspc
generates the same set of files that are generated by the JSP translator in an on-demand translation scenario and places them in or under your current directory, from which you ran ojspc
(not considering batch pretranslation).
Here are the files:
.sqlj
source file (for batch pretranslation, this is discarded after compilation)
.java
source file (for batch pretranslation, this is discarded after compilation)
.class
file for the page implementation class
.ser
), or optionally a .class
file, for the SQLJ profile
.res
) for the static text of the page
For more information about files that are generated by the JSP translator, see "Generated Files and Locations".
To summarize some of the commonly used options described under "Option Descriptions for ojspc", you can use the following ojspc
options to affect file generation and placement:
-appRoot
to specify an application root directory
-srcdir
to place source files in a specified location (not relevant for batch pretranslation)
-dir
to place binary files--.class
files and Java resource files--in a specified location (not relevant for batch pretranslation)
-noCompile
to not compile the generated page implementation class source
As a result of this, no .class
files are produced. In the case of SQLJ JSP pages, translated .java
files are still produced but not compiled.
-extres
to put static text into a Java resource file
-S-ser2class
(SQLJ -ser2class
option, for SQLJ JSP pages only, and for ISO standard SQLJ code generation only) to generate the SQLJ profile in a .class
file instead of a .ser
Java resource file
For output file placement, not considering batch pretranslation, the directory structure underneath the current directory (or directories specified by the -dir
and -srcdir
options, as applicable) is based on the package. The package is based on the location of the file being translated relative to the application root, which is either the current directory or the directory specified in the -appRoot
option.
For example, suppose you run ojspc
as follows (where %
is a UNIX prompt):
% cd /abc % ojspc def/ghi/test.jsp
Then the package is _def._ghi
and output files will be placed in the directory /abc/_def/_ghi
, where the _def/_ghi
subdirectory structure is created as part of the process.
If you specify alternate output locations through the -dir
and -srcdir
options, a _def/_ghi
subdirectory structure is created under the specified directories.
Now presume that you run ojspc
from some other directory, as follows:
% cd /home/mydir % ojspc -appRoot /abc /abc/def/ghi/test.jsp
The package is still _def._ghi
, according to the location of test.jsp
relative to the specified application root. Output files will be placed in the directory /home/mydir/_def/_ghi
or in a _def/_ghi
subdirectory under locations specified through the -dir
and -srcdir
options. In either case, the _def/_ghi
subdirectory structure is created as part of the process.
The following sections cover general deployment considerations and scenarios, mostly independent of your target environment:
This section provides an overview of OC4J deployment features and standard WAR deployment features.
See Oracle Application Server Containers for J2EE User's Guide for detailed information about deployment to OC4J in an Oracle Application Server environment.
In OC4J, deploy each application through a standard EAR (Enterprise archive) file. The name of the application and the name and location of the EAR file are specified through an <application>
element in the OC4J server.xml
file. This file is in the OC4J configuration files directory.
In an Oracle Application Server environment, use Enterprise Manager for deployment and configuration and do not update server.xml
or other configuration files directly. Refer to the Oracle Application Server 10g Administrator's Guide and Oracle Enterprise Manager Concepts for information.
In an OC4J standalone development environment, OC4J supports the admin.jar
tool for deployment. This modifies server.xml
, http-web-site.xml
, and other configuration files for you, based on settings you specify to the tool. Or you can modify the configuration files manually (not generally recommended). Note that if you modify configuration files in Oracle Application Server without going through Enterprise Manager, you must run the dcmctl
tool, using its updateConfig
command, to inform Oracle Application Server Distributed Configuration Management (DCM) of the updates. (This does not apply in an OC4J standalone mode, where OC4J is being run apart from Oracle Application Server.)
The dcmctl
tool is documented in the Oracle Application Server 10g Administrator's Guide.
The EAR file includes the following:
application.xml
configuration file, in /META-INF
orion-application.xml
configuration file, in /META-INF
The WAR file includes the following:
web.xml
configuration file, in /WEB-INF
In the web.xml
file for any particular application, you can override global settings for individual configuration parameters or for the definition of the JSP servlet (oracle.jsp.runtimev2.JspServlet
by default). Each application uses its own instance of the JSP servlet.
orion-web.xml
configuration file, in /WEB-INF
/WEB-INF/classes
and in JAR files in /WEB-INF/lib
See the Oracle Application Server Containers for J2EE User's Guide for more information about deployment to Oracle Application Server. See the Oracle Application Server Containers for J2EE Stand Alone User's Guide for deployment to a standalone environment and for information about admin.jar
. Also see "Key OC4J Configuration Files" for a summary of important configuration files in OC4J.
The JSP specification (since JSP 1.1) supports the packaging and deployment of Web applications, including JavaServer Pages, according to the servlet specification (since servlet 2.2).
In typical implementations, you can deploy JSP pages through the WAR mechanism, creating WAR files through the JAR utility. The JSP pages can be delivered in source form and are deployed along with any required support classes and static HTML files.
According to the servlet specification, a Web application includes a deployment descriptor file, web.xml
, that contains information about the JSP pages and other components of the application. The web.xml
file must be included in the WAR file.
The servlet specification also defines an XML DTD for web.xml
deployment descriptors and specifies exactly how a servlet container must deploy a Web application to conform to the deployment descriptor.
Through these logistics, a WAR file is the best way to ensure that a Web application is deployed into any standard servlet environment exactly as the developer intends.
Deployment configurations in the web.xml
deployment descriptor include mappings between servlet paths and the JSP pages and servlets that will be invoked. You can specify many additional features in web.xml
as well, such as timeout values for sessions, mappings of file name extensions to MIME types, and mappings of error codes to JSP error pages.
For more information about standard WAR deployment, see the Sun Microsystems Java Servlet Specification.
Oracle JDeveloper supports many types of deployment profiles, including simple archive, J2EE application (EAR file), J2EE EJB module (EJB JAR file), J2EE Web module (WAR file), J2EE client module (client JAR file), tag library for JSP 1.2 (tag library JAR file), business components EJB session bean profile, and business components archive profile.
When creating a Business Components for Java (BC4J) Web application using Oracle JDeveloper, a J2EE Web module deployment archive is generated, containing both the BC4J and the Web application files.
The JDeveloper deployment wizards create all the necessary code to deploy business components as a J2EE Web module. Typically, a JSP client accesses the BC4J application in a J2EE Web Module configuration. The JSP client can also use data tags, data Web beans, or UIX tags to access the business components. (See the Oracle Application Server Containers for J2EE JSP Tag Libraries and Utilities Reference for an overview of the BC4J and UIX tag libraries.)
A J2EE Web module is packaged as a WAR file that contains one or more Web components (servlets and JSP pages) and web.xml
, the deployment descriptor file.
JDeveloper lets you create the deployment profile containing the Web components and the web.xml
file, and packages them into a standard J2EE EAR file for deployment. JDeveloper takes the resulting EAR file and deploys it to one or more Oracle Application Server instances.
For information about JDeveloper, refer to the JDeveloper online help or to the following site on the Oracle Technology Network:
http://otn.oracle.com/products/jdev/content.html
JSP pages are typically used in an on-demand scenario, where pages are translated as they are invoked, in a sequence that is invisible to the user. Another approach is to pretranslate JSP pages, which offers at least two advantages:
You also might want to pretranslate pages so that you can deploy binary files only, as discussed in "Deployment of Binary Files Only".
OC4J users can employ the Oracle ojspc
utility, either specifying individual files for pretranslation or specifying archive files (JAR, WAR, EAR, or ZIP) for batch pretranslation. There is also a standard jsp_precompile
mechanism. These topics are covered in the following sections:
Also see "The ojspc Pretranslation Utility" for detailed information about this utility.
When you pretranslate with ojspc
(not considering batch pretranslation), use the -dir
option to set an appropriate output base directory for placement of generated binary files.
Consider the example in "JSP Translator Output File Locations", where the JSP page is located in the examples/jsp
subdirectory under the OC4J standalone default Web application directory:
j2ee/home/default-web-app/examples/jsp/welcome.jsp
A user would invoke this with a URL such as the following:
http://host:port/examples/jsp/welcome.jsp
(This is just a general example and does not consider OC4J configuration for the context path.)
In an on-demand translation scenario for this page, as explained in the example, the JSP translator would by default use the following base directory for placement of generated binary files:
j2ee/home/application-deployments/default/defaultWebApp/persistence/_pages/_examples/_jsp
When you pretranslate, set your current directory to the application root directory, then in ojspc
set the _pages
directory as the output base directory. This results in the appropriate package name and file hierarchy. Continuing the example (where %
is a UNIX prompt, OC4J_HOME
is the directory where OC4J is installed, and the ojspc
command wraps around to a second line):
% cd OC4J_HOME/j2ee/home/default-web-app % ojspc examples/jsp/welcome.jsp -dir OC4J_HOME/j2ee/home/application-deployments/default/defaultWebApp/persistence/_pages
(This assumes you specify the appropriate OC4J_HOME
directory.) The ojspc
command translates examples/jsp/welcome.jsp
and specifies the _pages
directory as the base output directory.
The URL noted above specifies an application-relative path of examples/jsp/welcome.jsp
, so at execution time the JSP container looks for the binary files in an _examples/_jsp
subdirectory under the _pages
directory. This subdirectory would be created automatically by ojspc
if it is run as in the above example.
At execution time, the JSP container would find the pretranslated binaries and would not have to perform translation, assuming that either the source file was not altered after pretranslation, or the JSP main_mode
flag is set to justrun
.
Beginning with the OC4J 9.0.3 implementation, there are ojspc
features for batch pretranslation of JSP files in archive files (JAR, WAR, EAR, or ZIP files). When you specify an archive file on the ojspc
command line, by default all .jsp
, .sqljsp
, .sqlj
, and .java
files in the contents will be pretranslated and compiled, as appropriate, and the archive file will be updated to include the output .class
files and any Java resource files (but not generated .java
or .sqlj
files). You would then deploy the resulting archive file.
In addition to this basic functionality, you can use key ojspc
options as follows:
-batchMask
option to specify file name extensions for pretranslation and compilation. Whatever you specify is instead of the defaults (*.jsp
, *.sqljsp
, *.sqlj
, and *.java
).
-output
option to specify a new archive file name. By default, ojspc
updates the original archive file, adding output .class
files and any resource files (and possibly deleting processed source files, according to the -deleteSource
option). If you want to be sure that the original archive file is unaltered, then enable the -output
option. In this case, all contents of the original archive file are copied into the specified archive file, then the specified file is updated instead of the original file. The original archive file is unaltered, and you would use the new file instead of the original file for deployment.
-deleteSource
option if you do not want processed source files to appear in the resulting archive file. If you do not also use the -output
option, this effectively means that all processed source files are removed from the original archive file after processing. If you do not use the -batchMask
option, this consists of all .jsp
, .sqljsp
, .sqlj
, and .java
files. Otherwise, this consists of all files specified in the -batchMask
setting.
It is also possible to specify JSP pretranslation without execution when you invoke the page in an on-demand scenario. Accomplish this as follows:
precompile_check
configuration parameter. (See "JSP Configuration Parameters".)
jsp_precompile
request parameter when you invoke the JSP page from the browser.
Following is an example of using jsp_precompile
:
http://host:port/foo.jsp?jsp_precompile=true
or:
http://host:port/foo.jsp?jsp_precompile
(The "=true
" is optional.)
Refer to the Sun Microsystems JavaServer Pages Specification for more information about this mode of operation.
You can avoid exposing your JSP source, for proprietary or security reasons, by pretranslating the pages and deploying only the translated and compiled binary files. Pages that are pretranslated, either from previous execution in an on-demand translation scenario or by using ojspc
, can be deployed to any standard J2EE environment. This involves two steps:
You must take steps to create and archive the binary files in an appropriate hierarchy.
ojspc
, you must first set your current directory to the application root directory. After running ojspc
, archive the output files using the ojspc
output directory as the base directory for the archive. See "The ojspc Pretranslation Utility" for general information about this utility.
_pages
directory.
In the target environment, place the archive JAR file in the /WEB-INF/lib
directory. Alternatively, restore the archived directory structure under the appropriate directory, typically under the _pages
directory.
If you have deployed binary files to an OC4J environment, set the JSP configuration parameter main_mode
to the value justrun
or reload
to execute JSP pages without the original source.
Without this setting, the JSP translator will always look for the JSP source file to see if it has been modified more recently than the page implementation .class
file, and will terminate with a "file not found" error if it cannot find the source file.
With main_mode
set appropriately, the user can invoke a page with the same URL that would be used if the source file were in place.
For how to set configuration parameters in the OC4J environment, see "Setting JSP Configuration Parameters in OC4J".
|
![]() Copyright © 2000, 2003 Oracle Corporation. All Rights Reserved. |
|