diff options
Diffstat (limited to 'docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html')
| -rw-r--r-- | docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html | 35 |
1 files changed, 21 insertions, 14 deletions
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html index fceb834d9..984877014 100644 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html +++ b/docs/org.eclipse.jst.j2ee.doc.user/topics/cjappcliproj.html @@ -11,9 +11,12 @@ <meta name="DC.Title" content="Application client projects" /> <meta name="abstract" content="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools." /> <meta name="description" content="Application client projects contain programs that run on networked client systems so the project can benefit from a server's tools." /> -<meta content="application client projects, overview, J2EE" name="DC.subject" /> -<meta content="application client projects, overview, J2EE" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/ph-projects.html" /> +<meta content="application client projects, overview, Java EE" name="DC.subject" /> +<meta content="application client projects, overview, Java EE" name="keywords" /> +<meta scheme="URI" name="DC.Relation" content="../topics/cjarch.html" /> +<meta scheme="URI" name="DC.Relation" content="../topics/tjappproj.html" /> +<meta scheme="URI" name="DC.Relation" content="../topics/tjexpapp.html" /> +<meta scheme="URI" name="DC.Relation" content="../topics/tjimpapp.html" /> <meta content="XHTML" name="DC.Format" /> <meta content="cjappcliproj" name="DC.Identifier" /> <meta content="en-us" name="DC.Language" /> @@ -36,11 +39,11 @@ a server's tools.</p> <p> Application client projects contain the resources needed for application client modules. An application client module is used to contain a full-function client Java™ application (non Web-based) that connects to and -uses the J2EE resources defined in your server. When you place the client +uses the Java EE resources defined in your server. When you place the client code in an application client module instead of a simple JAR file, the application client benefits from the server's resources (it does not need to re-specify -the class path to J2EE and server JAR files) as well as from easier JNDI lookup -(the client container fills in the initial context and other parameters). +the class path to Java EE and server JAR files) as well as from easier JNDI +lookup (the client container fills in the initial context and other parameters). The application client project allows you to work as if you are creating a standalone Java application in a Java project.</p> @@ -78,12 +81,12 @@ files, and deployment descriptor information and any meta-data extensions and bindings files.</p> <p>Application client projects are typically run on networked client systems -connected to J2EE (EJB) servers. The point of entry for the application client -is a Java main-class, -which is simply a Java class that contains a static main method. The class -is declared in the manifest file of the client module. </p> +connected to Java EE (EJB) servers. The point of entry for the application +client is a Java main-class, which is simply a Java class +that contains a static main method. The class is declared in the manifest +file of the client module. </p> -<p>A J2EE application client container provides access to the J2EE service +<p>A Java EE application client container provides access to the Java EE service (JNDI naming services, deployment services, transaction services, and security services) and communications APIs (internet protocols, Remote Method Invocation protocols, Object Management Group protocols, Messaging protocols, and data @@ -97,9 +100,13 @@ along with all the meta-data files in the <span class="uicontrol">META-INF</span </div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></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> +<div class="reltasks"><strong>Related tasks</strong><br /> +<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/tjexpapp.html" title="You can export an application client project as a JAR file.">Exporting an application client project</a></div> +<div><a href="../topics/tjimpapp.html" title="Application client projects are deployed as JAR files. You can import an application client project that has been deployed into a JAR file by using the Import wizard.">Importing an application client JAR file</a></div> </div> </div> |