#Glassfish directory structure archive

Invoke the addClassPath and addMetadata methods if you require them. To create a scattered archive, perform these tasks: Therefore, you must specify the location of the module's resources, deployment descriptor, and classes when deploying the module. In a scattered archive, these items are not required to be organized in a specific directory structure.

#Glassfish directory structure archive

Deploying a module from a scattered archive simplifies the testing of a module during development, especially if all the items that the module requires are not available to be packaged. Simply quote each parameter in the method, for example '-force=true'.ĭeploying a module from a scattered archive (WAR or JAR) enables you to deploy an unpackaged module whose resources, deployment descriptor, and classes are in any location. Specify the java.io.File class instance you created previously as the first method parameter.įor information about optional parameters you can set, see the descriptions of the deploy(1) subcommand parameters. Invoke the deploy (File archive, params ) method of the instance of the Deployer object. Invoke the getDeployer method of the GlassFish object to get an instance of the class. Instantiate the java.io.File class to represent the archive file or directory. If some of the resources needed by an application are not under the application's directory, see Creating a Scattered Archive. For more information about the requirements for deploying an application from a directory, see ' To Deploy an Application or Module in a Directory Format' in Oracle GlassFish Server Application Deployment Guide.

The directory must be accessible to the machine on which the deploying application runs. The contents of the directory must match the contents of the expanded Java EE archive file as laid out by the GlassFish Server. For more information, see ' Deploying Applications' in Oracle GlassFish Server Application Deployment Guide.ĭeploying an application from a directory enables you to deploy an application without the need to package the application in an archive file. The content of the file must be organized in the directory structure that the Java EE specifications define for the type of archive that the file contains. To Deploy an Application From an Archive File or a DirectoryĪn archive file contains the resources, deployment descriptor, and classes of an application. For an explanation of as-install, see Installation Root Directory. Do not move this file or it will not work. Reference this file from the as-install /lib/embedded directory of a nonembedded GlassFish Server installation. Must be used with a nonembedded installation of GlassFish Server. glassfish-embedded-static-shell.jarĬontains references to classes needed for deploying all Java EE application types. glassfish-embedded-all.jarĬontains classes needed for deploying all Java EE application types.

glassfish-embedded-web.jarĬontains classes needed for deploying Java EE web applications. To enable your applications to locate the class libraries for embedded GlassFish Server, add one of the following JAR files to your class path: glassfish-embedded-nucleus.jarĬorresponds to the nucleus distribution.