1. Overview of Oracle GlassFish Server 3.1 Application Deployment
A. The asadmin Deployment Subcommands
B. GlassFish Server Deployment Descriptor Files
C. Elements of the GlassFish Server Deployment Descriptors
activation-config-property-name
activation-config-property-value
check-version-of-accessed-instances
Contains the name of a custom JNLP file, which modifies the behavior of a Java Web Start enabled application client module. If none is specified, a default JNLP file is generated.
The value of this element is a relative path with the following format:
[path-to-JAR-in-EAR!]path-to-JNLP-in-JAR
The default path-to-JAR-in-EAR is the current application client JAR file. For example, if the JNLP file is in the application client JAR file at custom/myInfo.jnlp, the element value would look like this:
<java-web-start-access> <jnlp-doc>custom/myInfo.jnlp</jnlp-doc> </java-web-start-access>
If the application client is inside an EAR file, you can place the custom JNLP file inside another JAR file in the EAR. For example, if the JNLP file is in a JAR file at other/myLib.jar, the element value would look like this, with an exclamation point (!) separating the path to the JAR from the path in the JAR:
<java-web-start-access> <jnlp-doc>other/myLib.jar!custom/myInfo.jnlp</jnlp-doc> </java-web-start-access>
For information about the allowed contents of a custom JNLP file, see Chapter 10, Developing Java Clients, in Oracle GlassFish Server 3.1 Application Development Guide.
java-web-start-access (glassfish-application-client.xml)
none - contains data