Client Packaging

Target Audience and Content

The target audience for this guide is the Client component provider, i.e. the person in charge of developing the client components on the client side. It describes how the client components should be packaged.

The content of this guide is the following:

  1. Target Audience and Content
  2. Principles

Principles

Client components are packaged for deployment in a standard Java programming language Archive file, called a jar file (Java ARchive). The document root contains a subdirectory called META-INF, which contains the following files and directories:

The manifest of this client jar must contain the name of the class to launch (containing main method). This is described by the value of the Main-Class attribute of the manifest file.
In the case of a standalone client(not bundle in an Ear) you have to put all the Ejb classes (except the skeleton) on which you want to do lookup.

Example

The better way is to use ant with build.xml file. You have two examples of building a java client.