Automatic deployment, also called autodeployment, involves copying an application or module file (JAR, WAR, RAR, or EAR) into a special directory, where it is automatically deployed by the Enterprise Server. To undeploy an automatically deployed application or module, simply remove its file from the special autodeployment directory. This is useful in a development environment, because it allows new code to be tested quickly. This feature is available only on the default server instance.
Autodeployment of a web services JSR 181 annotated file is supported. For more information, see JSR 181 and Chapter 6, Developing Web Services, in Sun GlassFish Enterprise Server 2.1 Developer’s Guide.
Autodeployment is enabled by default.
To access autodeployment features:
In the developer profile:
In the cluster profile:
Check the Auto Deploy Enabled box to enable autodeployment, or uncheck this box to disable autodeployment.
Enter a number of seconds in the Auto Deploy Poll Interval field.
This sets the interval at which applications and modules are checked for code changes and dynamically reloaded. The default is 2.
You can change the Auto Deploy Directory.
You can enter an absolute or relative path. A relative path is relative to domain-dir. The default is domain-dir/autodeploy.
You can check the Verifier Enabled box to verify your deployment descriptor files. This is optional.
For details about the verifier, see The verifier Utility.
Check the Precompile Enabled box to precompile any JSP files.
For details, click the Help button in the Admin Console.