| <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html lang="en-us" xml:lang="en-us"> |
| <head> |
| <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> |
| <meta name="copyright" content="Copyright (c) 2000, 2009 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at https://www.eclipse.org/legal/epl-2.0/. Contributors: IBM Corporation - initial API and implementation" /> |
| <meta name="DC.rights.owner" content="(C) Copyright 2000, 2009" /> |
| <meta content="public" name="security" /> |
| <meta content="index,follow" name="Robots" /> |
| <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> |
| <meta content="concept" name="DC.Type" /> |
| <meta name="DC.Title" content="Enterprise application projects" /> |
| <meta name="abstract" content="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application." /> |
| <meta name="description" content="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application." /> |
| <meta content="enterprise applications, projects, artifacts, J2EE, enterprise application projects, overview" name="DC.subject" /> |
| <meta content="enterprise applications, projects, artifacts, J2EE, enterprise application projects, overview" name="keywords" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjimpear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjexpear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjear.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/tjrar.html" /> |
| <meta scheme="URI" name="DC.Relation" content="../topics/cfacets.html" /> |
| <meta content="XHTML" name="DC.Format" /> |
| <meta content="cjearproj" name="DC.Identifier" /> |
| <meta content="en-us" name="DC.Language" /> |
| <link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> |
| <title>Enterprise application projects</title> |
| </head> |
| <body id="cjearproj"><a name="cjearproj"><!-- --></a> |
| |
| |
| <h1 class="id_title">Enterprise application projects</h1> |
| |
| |
| |
| <div class="id_conbody"><p class="id_shortdesc">An enterprise application project ties |
| together the resources that are required to deploy a J2EE enterprise application.</p> |
| |
| <p class="anchor_topictop" /> |
| |
| <p>An enterprise application project contains a set of references to other |
| J2EE modules and Java™ projects that are combined to compose an EAR file. |
| These projects can be Web modules, EJB modules, application client modules, |
| connector modules, general utility Java JAR files, and EJB client JAR files. |
| Enterprise application projects created in the workbench include a deployment |
| descriptor, as well as files that are common to all J2EE modules that are |
| defined in the deployment descriptor.</p> |
| |
| <p>When a J2EE module project is created, it can be associated with an enterprise |
| application project. The project wizards aid this by allowing you to specify |
| a new or existing enterprise application project. Enterprise application projects |
| are exported as EAR (enterprise archive) files that include all files defined |
| in the Enterprise Application project as well as the appropriate archive file |
| for each J2EE module or utility JAR project defined in the deployment descriptor, |
| such as Web archive (WAR) files and EJB JAR files.</p> |
| |
| <p>An enterprise application can contain utility JAR files that are to be |
| used by the contained modules. This allows sharing of code at the application |
| level by multiple Web, EJB, or application client modules. These JAR files |
| are commonly referred to as utility JAR files. The utility JAR files defined |
| for an enterprise application project can be actual JAR files in the project, |
| or you can include utility Java projects that are designated to become |
| the utility JAR files during assembly and deployment.</p> |
| |
| <p>To start developing J2EE applications, you typically first create an enterprise |
| application project to tie together your Web, EJB, and application client |
| modules. The enterprise application project is used to compose an entire application |
| from the various modules. Since no source code is built directly into an enterprise |
| application, these projects are not Java projects, and they are not compiled |
| by the Java builder.</p> |
| |
| <div class="p">When you create an enterprise application project using the workbench, |
| the following key files are automatically created:<dl> |
| <dt class="dlterm">META-INF/application.xml</dt> |
| |
| <dd>This file is the deployment descriptor for the enterprise application, |
| as defined in the J2EE specification, that is responsible for associating |
| J2EE modules to a specific EAR file. This file is created in the <span class="uicontrol">META-INF</span> folder.</dd> |
| |
| |
| <dt class="dlterm">.settings/.component</dt> |
| |
| <dd>This file matches the location of each module's source code to the location |
| of the module at deployment. For each module included for deployment with |
| the EAR file, the .component file lists its source path and deployment path. |
| This file is created in the <span class="uicontrol">.settings</span> folder.</dd> |
| |
| |
| <dt class="dlterm">.settings/org.eclipse.wst.common.project.facet.core.xml</dt> |
| |
| <dd>This file lists the facets of the enterprise application project. See <a href="cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration. ">Project facets</a>. This file is created in the <span class="uicontrol">.settings</span> folder.</dd> |
| |
| |
| <dt class="dlterm">.project</dt> |
| |
| <dd>This is a workbench artifact, the standard project description file.</dd> |
| |
| </dl> |
| </div> |
| |
| <p class="anchor_topicbottom" /> |
| |
| </div> |
| |
| <div><div class="relconcepts"><strong>Related concepts</strong><br /> |
| <div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise applications.">J2EE architecture</a></div> |
| <div><a href="../topics/cfacets.html" title="Facets define characteristics and requirements for Java EE projects and are used as part of the runtime configuration.">Project facets</a></div> |
| </div> |
| <div class="reltasks"><strong>Related tasks</strong><br /> |
| <div><a href="../topics/tjear.html" title="Using the wizard to create an enterprise application project allows you to package many web applications and modules in a project and deploy these modules as a J2EE enterprise application.">Creating an enterprise application project</a></div> |
| <div><a href="../topics/tjimpear.html" title="Enterprise application projects are deployed into EAR files. You can import an enterprise application project by importing it from a deployed EAR file.">Importing an enterprise application EAR file</a></div> |
| <div><a href="../topics/tjexpear.html" title="Enterprise applications are deployed in the form of an EAR file. Use the Export wizard to export an enterprise application project into an EAR file for deployment.">Exporting an enterprise application into an EAR file</a></div> |
| <div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div> |
| <div><a href="../topics/tjrar.html" title="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).">Creating a connector project</a></div> |
| </div> |
| </div> |
| |
| </body> |
| </html> |
