Updated May 30, 2001
The sample applications included as part of iPlanet Application Server are packaged according to a consistent diretcory structure. This structure is meant to represent a realistic approach to defining source code workspaces for J2EE applications. If you are establishing a source code directory structure for your own J2EE applications, you will find it useful to review the layout of the sample application source directories and how they are used in the Ant-based build environment.
The larger sample applications such as Bank and Java Pet Store are located directly under the the <iAS install path>/ias/ias-samples/ directory while the balance of the samples are arranged under various categories within the ias-samples/ directory. For example, Java Message Service (JMS) samples are collected under ias-samples/jms/<samplename>/.
Within each sample, the following directories and/or files exist:
| Directory or File | Description |
| <sampleroot>/ | |
|
pre-built J2EE EAR file. |
|
sample setup instructions. |
|
location of Javadoc information when using "build javadocs" to generate API documentation for a sample. |
|
sample source code. Contains J2EE deployment descriptors. |
|
database setup scripts and DDL. |
|
web content: JSPs, HTML, images, etc. |
|
Tag library definition and resource files. |
|
Java source code. |
|
transient build area. |
|
class files generated by build facility. |
|
transient assembly area. |
|
EAR file assembly area. |
|
WAR file assembly area. |
|
EJB JAR file assembly area. |
Since the Java Pet Store application is supplied by Sun Microsystems, the directory structure of this sample is slightly different from the other sample applications.
Here's a file explorer view of the sample applications: