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:
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 the main method). This is defined by the value of the
Main-Class attribute of the manifest file.
For a standalone client (not bundled in an Ear), all the Ejb classes (except
the skeleton) on which lookups will be performed must be included.
Two examples of building a java client are provided.