Specifies a method.
message (sun-web.xml, sun-ejb-jar.xml, sun-application-client.xml)
The following table describes subelements for the java-method element.
Table A–53 java-method Subelements
Element |
Required |
Description |
---|---|---|
only one |
Specifies a method name. |
|
zero or one |
Specifies fully qualified Java type names of method parameters. |
Specifies changes to default Java Web Start parameters for an embedded or stand-alone application client module.
sun-application-client (sun-application-client.xml)
The following table describes subelements for the java-web-start-access element.
Table A–54 java-web-start-access subelements
Element |
Required |
Description |
||
---|---|---|---|---|
zero or one |
Contains the context root for the Java Web Start enabled application client module. If none is specified, a default is generated. The default for an application is as follows:
The default for a stand-alone application client module is as follows:
If the app-name or module-name is not specified during deployment, the name of the EAR or JAR file without the extension is used. If the application or module is not in EAR or JAR file format, a name is generated and written to the server log. |
|||
zero or one |
Specifies whether the application client module is eligible to be Java Web Start enabled. Allowed values are true (the default) and false. |
|||
zero or one |
Specifies the name of the vendor as it appears in Java Web Start download and launch screens. The default value is Application Client. |
Specifies the durable subscription associated with a message-driven bean class. Only applies to the Java Message Service Topic Destination type, and only when the message-driven bean deployment descriptor subscription durability is Durable.
ejb (sun-ejb-jar.xml)
none - contains data
Specifies the maximum number of messages to load into a Java Message Service session at one time for a message-driven bean to serve. The default is 1.
ejb (sun-ejb-jar.xml)
none - contains data
Specifies the absolute jndi-name of a URL resource or a resource.
For entity beans and session beans, this value specifies the global JNDI name of the EJBHome object. It is only needed if the entity or session bean exposes a remote view.
For JMS message-driven beans, this is the JNDI name of the JMS resource from which the message-driven bean consumes JMS messages. This information is alternatively specified within the activation-config subelement of the mdb-resource-adapter element. For more information about JMS resources, see Chapter 18, Using the Java Message Service, in Sun GlassFish Enterprise Server v2.1.1 Developer’s Guide.
ejb-ref, message-destination, resource-env-ref, resource-ref (sun-web.xml, sun-ejb-jar.xml, sun-application-client.xml); cmp-resource, ejb, mdb-connection-factory (sun-ejb-jar.xml)
none - contains data
Specifies JSP configuration information.
sun-web-app (sun-web.xml)
The following table describes subelements for the jsp-config element.
Table A–55 jsp-config Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a property, which has a name and a value. |
The default property values are tuned for development of JSP files at the cost of performance. To maximize performance, set jsp-config properties to these non-default values:
development - false (as an alternative, set to true and give modificationTestInterval a large value)
mappedfile - false
trimSpaces - true
suppressSmap - true
fork - false (on Solaris)
classdebuginfo - false
The following table describes properties for the jsp-config element.
Table A–56 jsp-config Properties
Property |
Default |
Description |
---|---|---|
0 |
If development is set to false and checkInterval is greater than zero, background compilations are enabled. The checkInterval is the time in seconds between checks to see if a JSP file needs to be recompiled. |
|
true |
Specifies whether the generated Java servlets are compiled with the debug option set (-g for javac). |
|
created dynamically based on the current web application |
Specifies the classpath to use when compiling generated servlets. |
|
javac |
Specifies the compiler Ant uses to compile JSP files. See the Ant documentation for more information: |
|
Depends on the Enterprise Server's Java runtime |
Specifies the JDK release with which source compatibility of the generated servlets is provided. Same as the -source release option of javac. For more information, see http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html#options. |
|
Depends on the Enterprise Server's Java runtime |
Specifies the JVM version for which the servlet class files are generated. Same as the -target release option of javac. For more information, see http://java.sun.com/javase/6/docs/technotes/tools/solaris/javac.html#options. |
|
false |
If true, the default for the buffer attribute of the page directive is none. |
|
true |
If set to true, enables development mode, which allows JSP files to be checked for modification. Specify the frequency at which JSPs are checked using the modificationTestInterval property. |
|
false |
If set to true, dumps SMAP information for JSR 45 debugging to a file. Set to false if suppressSmap is true. |
|
true |
If set to true, tag handler pooling is enabled. |
|
false |
If set to true, all Tag Library Descriptor (TLD) files referenced by the web application are validated against their underlying schema or DTD file. |
|
false |
If set to true, issues an error when the value of the class attribute in a useBean action is not a valid bean class. |
|
true |
Specifies that Ant forks the compiling of JSP files, using a JVM separate from the one in which Tomcat is running. |
|
true |
If true, text strings are generated as bytes (encoded with the page encoding), if the page is not buffered. |
|
false |
If set to true, generates text strings as char arrays, which improves performance in some cases. |
|
* for all methods |
Specifies a comma separated list of HTTP methods supported by the JspServlet. |
|
clsid:8AD9C840-044E-11D1-B3E9-00805F499D93 |
Specifies the Java plug-in COM class ID for Internet Explorer. Used by the <jsp:plugin> tags. |
|
false |
If set to true, instructs the compiler to ignore any JSP precompilation errors pertaining to statically included JSP segments that, despite not being top level JSP files, use the .jsp or .jspx extension (instead of the recommended .jspf). |
|
32 |
Specifies the initial capacity of the HashMap that maps JSP files to their corresponding servlets. |
|
UTF8 |
Specifies the encoding for the generated Java servlet. This encoding is passed to the Java compiler that is used to compile the servlet as well. By default, the web container tries to use UTF8. If that fails, it tries to use the javaEncoding value. For encodings, see: http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html |
|
true with JDK 5 and before and for jspc, otherwise false |
If set to true, keeps the generated Java files. If false, deletes the Java files. |
|
true |
If set to true, generates static content with one print statement per input line, to ease debugging. |
|
0 |
Specifies the frequency in seconds at which JSPs are checked for modification. A value of 0 causes the JSP to be checked on every access. Used only if development is set to true. |
|
0 |
Specifies the frequency in seconds at which JSP files are checked for modifications. Setting this value to 0 checks JSP files for modifications on every request. Setting this value to -1 disables checks for JSP modifications and JSP recompilation. |
|
true for jspc, otherwise false |
If true, generated byte code is saved to .class files? This option is meaningful only when the Java compiler API, JSR 199 (available with and used as the default on Java 6) is used for javac compilations. |
|
The default work directory for the web application |
Specifies the working directory created for storing all the generated code. |
|
false |
If set to true, generation of SMAP information for JSR 45 debugging is suppressed. |
|
false |
If set to true, trims white spaces in template text between actions or directives. |
|
false |
If set to true, an accessed JSP file is not compiled. Its precompiled servlet class is used instead. It is assumed that JSP files have been precompiled, and their corresponding servlet classes have been bundled in the web application’s WEB-INF/lib or WEB-INF/classes directory. |
|
true |
If set to true, the X-Powered-By response header is added by the generated servlet. |