You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by mb...@apache.org on 2008/06/20 17:10:32 UTC
svn commit: r669930 - in /incubator/uima/site/trunk/uima-website:
docs/doc-uima-pears.html xdocs/doc-uima-pears.xml
Author: mbaessler
Date: Fri Jun 20 08:10:32 2008
New Revision: 669930
URL: http://svn.apache.org/viewvc?rev=669930&view=rev
Log:
UIMA-1083
update UIMA Getting Started "Working with PEARs"
https://issues.apache.org/jira/browse/UIMA-1083
Modified:
incubator/uima/site/trunk/uima-website/docs/doc-uima-pears.html
incubator/uima/site/trunk/uima-website/xdocs/doc-uima-pears.xml
Modified: incubator/uima/site/trunk/uima-website/docs/doc-uima-pears.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/doc-uima-pears.html?rev=669930&r1=669929&r2=669930&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/doc-uima-pears.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/doc-uima-pears.html Fri Jun 20 08:10:32 2008
@@ -163,8 +163,8 @@
<blockquote>
<p>
The "Getting Started: Working With PEARs"
- guide should help you to understand what a PEAR (Processing Engine ARchive) file is
- and how PEARS can easily be used and integrated into UIMA applications.
+ guide should help you to understand what a PEAR package is,
+ how to generate them and how to use them within UIMA applications.
</p>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
@@ -179,10 +179,10 @@
<p>
A PEAR (Processing Engine ARchive) file is the UIMA standard packaging format for UIMA components like
analysis engines (annotators) or CAS consumers. The PEAR package can be used to distribute
- and reuse components within other components or applications. The UIMA framework also provides
- APIs and methods to automatically deploy, verify and run PEAR packages. So when having a correct
- packaged PEAR, the application doesn't need any additional information or any manual deployed settings to
- run the PEAR package.
+ and reuse components within UIMA applications. The UIMA framework also provides
+ APIs and methods to automatically deploy, verify and run PEAR packages. When having a valid
+ packaged PEAR, the application doesn't need any additional information or any manual deployed settings
+ like classpath settings to run the packaged component.
</p>
<p>
To guarantee these characteristics, each PEAR package has the same internal
@@ -197,7 +197,7 @@
<li>
<p>
<b>metadata</b> - The metadata folder contains the PEAR package installation descriptor
- that contains all the necessary information about the PEAR package.
+ (<code>install.xml</code>) that hosts all the necessary information about the PEAR package.
</p>
</li>
<li>
@@ -247,14 +247,14 @@
</table>
</p>
<p>
- The most important file in a PEAR package is the installation descriptor (metadata/install.xml) that contains
- all the necessary information about the PEAR package. It it used to install and run the PEAR package
- and defines all necessary dependencies and settings. These are for example the ID/name of the PEAR package,
+ The most important file in a PEAR package is the installation descriptor (<code>metadata/install.xml</code>)
+ that contains all the necessary information about the PEAR package. It it used to install and run the PEAR
+ package and defines all dependencies and settings. These are for example the ID/name of the PEAR package,
Java classpath settings, UIMA datapath settings or the descriptor file that should be used to
run the PEAR package component. For more details about the installation descriptor,
please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installation_descriptor">
- Documented template for the installation descriptor</a>
+ Documented template for the installation descriptor</a>.
</p>
</blockquote>
</td></tr>
@@ -272,18 +272,18 @@
<blockquote>
<p>
In this section we will discuss how to generate a PEAR package. The UIMA framework distribution provides
- different possibilities to create PEAR packages. The details are discussed below.
+ different possibilities to create PEAR packages which are discussed below.
</p>
<p>
A more general thing that should be recognized independent of the PEAR packaging method are the
- PEAR macros or PEAR variables. The PEAR structure defines different macros or variables, but the most
+ PEAR macros or PEAR variables. The PEAR architecture defines different macros, but the most
important one is the <code>$main_root</code> macro. When using this macro in the installation descriptor
or within a UIMA descriptor it will be substituted with the real PEAR package installation
path to the main component root directory after the PEAR package is installed on the target system.
- For example, this macro should be used to specify the classpath settings for a PEAR component
+ For example, this macro can be used to specify the classpath settings for a PEAR component
as shown in some of the examples below. This guarantees that in each scenario the classpath settings
- are interpreted correctly. For more details about PEAR macros or PEAR variables, please refer to the
- UIMA documentation at
+ are interpreted correctly since an absolute path the jar file is used. For more details about PEAR macros,
+ please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installation_descriptor">
Documented template for the installation descriptor</a>.
</p>
@@ -293,8 +293,9 @@
<h4>PearPackaging Eclipse plugin</h4>
<p>
The PearPackaging Eclipse plugin is automatically installed in your Eclipse environment if you have
- installed the UIMA Eclipse plugins. The plugin allows you to package a PEAR based on the content of
- an eclipse project having a UIMA nature. This plugin can for example be used in an analysis engine
+ installed the <a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/overview_and_setup/overview_and_setup.html#ugr.ovv.eclipse_setup.install_uima_eclipse_plugins">
+ UIMA Eclipse plugins</a>. The PearPackaging plugin allows you to package a PEAR based on the content of
+ an eclipse project that has a UIMA nature. This plugin can for example be used in an analysis engine
development environment. I will not give more details here since it
is already explained in the <a href="http://incubator.apache.org/uima/doc-uima-annotator.html#Packaging the annotator">
Getting Started: Writing My First UIMA Annotator</a> guide.
@@ -304,7 +305,7 @@
<h4>PearPackaging Ant task</h4>
<p>
The PEAR packaging Ant task can be used in an Ant build environment to create PEAR packages for UIMA
- components. The PEAR package content as well as the PEAR package settings can be specified.
+ components. The PEAR package content as well as the PEAR package settings can be specified within the build.
An example how this can look like is shown below:
</p>
<p>
@@ -325,7 +326,7 @@
</td></tr></table>
</p>
<p>
- For additional information on how to integrate the PEAR packaging Ant taks, please refer to the
+ For additional information on how to integrate the PEAR packaging Ant task, please refer to the
<a href="http://svn.apache.org/repos/asf/incubator/uima/sandbox/trunk/PearPackagingAntTask/doc/pdf/PearPackagingAntTaskUserGuide.pdf">
PEAR packaging Ant task documentation</a>.
</p>
@@ -335,8 +336,8 @@
<h4>PearPackaging Maven plugin</h4>
<p>
The PEAR packaging Maven plugin can be used in a Maven build environment to create PEAR
- packages for UIMA component. The PEAR package content as well as the PEAR package settings
- can be specified. An example how this can look like is shown below:
+ packages for UIMA components. The PEAR package content as well as the PEAR package settings
+ can be specified in the POM (Project Object Model). An example how this can look like is shown below:
</p>
<p>
<table cellpadding="10"><tr><td bgcolor="lightgrey">
@@ -377,23 +378,23 @@
<li>
<h4>PearPackaging command line</h4>
<p>
- The PearPackaging command line can be used if script files should be used to create PEAR packages.
+ The PearPackaging command line can be used if scripting should be used to create PEAR packages.
Details about how to use the PearPackaging command line is available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tools/tools.html#ugr.tools.pear.packager.using_command_line">
Using the PEAR command line packager</a>.
</p>
</li>
<li>
- <h4>PearPackaging API</h4>
+ <h4>PEAR packaging API</h4>
<p>
If there is a need to create PEAR packages out of Java source code, the PEAR packaging
- API can be used. With the API is either possible to create complete PEAR packages or to create the PEAR
+ API can be used. With that API it is either possible to create complete PEAR packages or to create the PEAR
packages step by step - first create the installation descriptor and later package the PEAR. Detailed
information about the PEAR packaging API is available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.packaging_into_1_file">
Packaging the PEAR structure into one file</a> and in the
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/api/index.html?org/apache/uima/pear/tools/PackageCreator.html">
- JavaDocs</a>.
+ PEAR packaging API JavaDocs</a>.
</p>
</li>
</ul>
@@ -413,9 +414,9 @@
<tr><td>
<blockquote>
<p>
- But before a component that is packaged as PEAR can be used in an application, the PEAR package
+ But before a component that is packaged as PEAR can be used in a UIMA application, the PEAR package
must be installed on the target system. During the installation, the package content is extracted
- and the internal PEAR settings (PEAR macros) are updated with some target system information.
+ and the internal PEAR settings (PEAR macros) are updated with some install information.
This also means that an installed PEAR package cannot be moved to
another directory without any internal changes. By default the PEAR packages are not installed directly
to the specified installation directory. For each PEAR a subdirectory with the name of the PEAR's ID
@@ -424,7 +425,7 @@
</p>
<p>
To check the most important PEAR settings (classpath, datapath, ...), or to read the settings with an
- application a <code>setenv.txt</code> file containing all these information is generated in the
+ application a <code>setenv.txt</code> file containing the PEAR settings is generated in the
<code>metadata</code> directory during the installation.
</p>
<p>
@@ -437,21 +438,21 @@
UIMA application out of the box. For details about the PEAR descriptor, please refer to the
UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.specifier">
- PEAR package descriptor</a>
+ PEAR package descriptor</a>.
</p>
<p>
- To install a PEAR package you have two possibilities.
+ To install a PEAR package you have two options:
</p>
<p>
<ul>
<li>
- <h4>PearInstaller UI</h4>
+ <h4>PEAR Installer UI</h4>
<p>
- The PearInstaller UI is a standalone Swing application to install PEAR packages.
- AFter the PEAR package and the install directory is selected, the installaion is
+ The PEAR Installer UI is a standalone Swing application to install PEAR packages.
+ After the PEAR package and the install directory is selected, the installation is
performed and the installation and verification results are displayed. Out of the tool
- it is also possible to test the installed PEAR package directly using the Cas Visual Debugger.
- For more details about PearInstall, please refer to the UIMA documentation at
+ it is directly possible to test the installed PEAR package using the Cas Visual Debugger (CVD).
+ For more details about the PEAR Installer, please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tools/tools.html#ugr.tools.pear.installer">
PEAR Installer User's Guide</a>.
</p>
@@ -459,10 +460,10 @@
<li>
<h4>PEAR API</h4>
<p>
- The PearInstaller API should be used if you want to integrate the PEAR installation
+ The PEAR API should be used if you want to integrate the PEAR installation
with a custom application. With the PEAR API it is possible to install PEAR packages
to a given installation directory and to optional verify the installed packages.
- Details about the PearInstaller API are available in the UIMA documentation at
+ Details about the PEAR API are available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installing_pear_using_API">
Installing a PEAR file using the PEAR APIs</a>.
</p>
@@ -496,7 +497,7 @@
The PEAR package descriptor can be treated similar to an analysis engine descriptor. It can be added
at any place where an analysis engine descriptor or cas consumer descriptor can be used. So for example
to run an installed PEAR package in the CAS Visual Debugger or in the Document Analyzer just use
- the PEAR package descriptor as analysis engine - and you don't have to take care about classpath
+ the PEAR package descriptor as analysis engine - you don't have to take care about classpath
and datapath settings.
</p>
<p>
Modified: incubator/uima/site/trunk/uima-website/xdocs/doc-uima-pears.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/doc-uima-pears.xml?rev=669930&r1=669929&r2=669930&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/doc-uima-pears.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/doc-uima-pears.xml Fri Jun 20 08:10:32 2008
@@ -33,35 +33,18 @@
name="Getting Started: Working With PEARs">
<p>
The "Getting Started: Working With PEARs"
- guide should help you to understand what a PEAR (Processing Engine ARchive) file is
- and how PEARS can easily be used and integrated into UIMA applications.
+ guide should help you to understand what a PEAR package is,
+ how to generate them and how to use them within UIMA applications.
</p>
-
- <!--
- Content:
- - What are PEAR files
- - PEAR file structure
- - Generating PEARs (explained in another tutorial)
- - PEAR packaging plugin
- - Ant/Maven build
- - CommandLine
- - PEAR packaging API
- - Installing PEARs (environemnt variables, classpath, PEAR desc, not movable after installation)
- - PearInstaller, PEAR intall API
- - Integrating PEARs into an analysis chain
- - Running PEARs in DocumentAnalyzer or CVD
- - Running PEARs in an UIMA application
-
- -->
<subsection name="What are UIMA PEAR files">
<p>
A PEAR (Processing Engine ARchive) file is the UIMA standard packaging format for UIMA components like
analysis engines (annotators) or CAS consumers. The PEAR package can be used to distribute
- and reuse components within other components or applications. The UIMA framework also provides
- APIs and methods to automatically deploy, verify and run PEAR packages. So when having a correct
- packaged PEAR, the application doesn't need any additional information or any manual deployed settings to
- run the PEAR package.
+ and reuse components within UIMA applications. The UIMA framework also provides
+ APIs and methods to automatically deploy, verify and run PEAR packages. When having a valid
+ packaged PEAR, the application doesn't need any additional information or any manual deployed settings
+ like classpath settings to run the packaged component.
</p>
<p>
To guarantee these characteristics, each PEAR package has the same internal
@@ -76,7 +59,7 @@
<li>
<p>
<b>metadata</b> - The metadata folder contains the PEAR package installation descriptor
- that contains all the necessary information about the PEAR package.
+ (<code>install.xml</code>) that hosts all the necessary information about the PEAR package.
</p>
</li>
<li>
@@ -126,31 +109,31 @@
</table>
</p>
<p>
- The most important file in a PEAR package is the installation descriptor (metadata/install.xml) that contains
- all the necessary information about the PEAR package. It it used to install and run the PEAR package
- and defines all necessary dependencies and settings. These are for example the ID/name of the PEAR package,
+ The most important file in a PEAR package is the installation descriptor (<code>metadata/install.xml</code>)
+ that contains all the necessary information about the PEAR package. It it used to install and run the PEAR
+ package and defines all dependencies and settings. These are for example the ID/name of the PEAR package,
Java classpath settings, UIMA datapath settings or the descriptor file that should be used to
run the PEAR package component. For more details about the installation descriptor,
please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installation_descriptor">
- Documented template for the installation descriptor</a>
+ Documented template for the installation descriptor</a>.
</p>
</subsection>
<subsection name="Generating PEAR files">
<p>
In this section we will discuss how to generate a PEAR package. The UIMA framework distribution provides
- different possibilities to create PEAR packages. The details are discussed below.
+ different possibilities to create PEAR packages which are discussed below.
</p>
<p>
A more general thing that should be recognized independent of the PEAR packaging method are the
- PEAR macros or PEAR variables. The PEAR structure defines different macros or variables, but the most
+ PEAR macros or PEAR variables. The PEAR architecture defines different macros, but the most
important one is the <code>$main_root</code> macro. When using this macro in the installation descriptor
or within a UIMA descriptor it will be substituted with the real PEAR package installation
path to the main component root directory after the PEAR package is installed on the target system.
- For example, this macro should be used to specify the classpath settings for a PEAR component
+ For example, this macro can be used to specify the classpath settings for a PEAR component
as shown in some of the examples below. This guarantees that in each scenario the classpath settings
- are interpreted correctly. For more details about PEAR macros or PEAR variables, please refer to the
- UIMA documentation at
+ are interpreted correctly since an absolute path the jar file is used. For more details about PEAR macros,
+ please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installation_descriptor">
Documented template for the installation descriptor</a>.
</p>
@@ -161,8 +144,9 @@
<h4>PearPackaging Eclipse plugin</h4>
<p>
The PearPackaging Eclipse plugin is automatically installed in your Eclipse environment if you have
- installed the UIMA Eclipse plugins. The plugin allows you to package a PEAR based on the content of
- an eclipse project having a UIMA nature. This plugin can for example be used in an analysis engine
+ installed the <a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/overview_and_setup/overview_and_setup.html#ugr.ovv.eclipse_setup.install_uima_eclipse_plugins">
+ UIMA Eclipse plugins</a>. The PearPackaging plugin allows you to package a PEAR based on the content of
+ an eclipse project that has a UIMA nature. This plugin can for example be used in an analysis engine
development environment. I will not give more details here since it
is already explained in the <a href="http://incubator.apache.org/uima/doc-uima-annotator.html#Packaging the annotator">
Getting Started: Writing My First UIMA Annotator</a> guide.
@@ -172,7 +156,7 @@
<h4>PearPackaging Ant task</h4>
<p>
The PEAR packaging Ant task can be used in an Ant build environment to create PEAR packages for UIMA
- components. The PEAR package content as well as the PEAR package settings can be specified.
+ components. The PEAR package content as well as the PEAR package settings can be specified within the build.
An example how this can look like is shown below:
</p>
<p>
@@ -193,7 +177,7 @@
</td></tr></table>
</p>
<p>
- For additional information on how to integrate the PEAR packaging Ant taks, please refer to the
+ For additional information on how to integrate the PEAR packaging Ant task, please refer to the
<a href="http://svn.apache.org/repos/asf/incubator/uima/sandbox/trunk/PearPackagingAntTask/doc/pdf/PearPackagingAntTaskUserGuide.pdf">
PEAR packaging Ant task documentation</a>.
</p>
@@ -203,8 +187,8 @@
<h4>PearPackaging Maven plugin</h4>
<p>
The PEAR packaging Maven plugin can be used in a Maven build environment to create PEAR
- packages for UIMA component. The PEAR package content as well as the PEAR package settings
- can be specified. An example how this can look like is shown below:
+ packages for UIMA components. The PEAR package content as well as the PEAR package settings
+ can be specified in the POM (Project Object Model). An example how this can look like is shown below:
</p>
<p>
<table cellpadding="10"><tr><td bgcolor="lightgrey">
@@ -245,23 +229,23 @@
<li>
<h4>PearPackaging command line</h4>
<p>
- The PearPackaging command line can be used if script files should be used to create PEAR packages.
+ The PearPackaging command line can be used if scripting should be used to create PEAR packages.
Details about how to use the PearPackaging command line is available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tools/tools.html#ugr.tools.pear.packager.using_command_line">
Using the PEAR command line packager</a>.
</p>
</li>
<li>
- <h4>PearPackaging API</h4>
+ <h4>PEAR packaging API</h4>
<p>
If there is a need to create PEAR packages out of Java source code, the PEAR packaging
- API can be used. With the API is either possible to create complete PEAR packages or to create the PEAR
+ API can be used. With that API it is either possible to create complete PEAR packages or to create the PEAR
packages step by step - first create the installation descriptor and later package the PEAR. Detailed
information about the PEAR packaging API is available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.packaging_into_1_file">
Packaging the PEAR structure into one file</a> and in the
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/api/index.html?org/apache/uima/pear/tools/PackageCreator.html">
- JavaDocs</a>.
+ PEAR packaging API JavaDocs</a>.
</p>
</li>
</ul>
@@ -269,9 +253,9 @@
</subsection>
<subsection name="Installing PEAR files">
<p>
- But before a component that is packaged as PEAR can be used in an application, the PEAR package
+ But before a component that is packaged as PEAR can be used in a UIMA application, the PEAR package
must be installed on the target system. During the installation, the package content is extracted
- and the internal PEAR settings (PEAR macros) are updated with some target system information.
+ and the internal PEAR settings (PEAR macros) are updated with some install information.
This also means that an installed PEAR package cannot be moved to
another directory without any internal changes. By default the PEAR packages are not installed directly
to the specified installation directory. For each PEAR a subdirectory with the name of the PEAR's ID
@@ -280,7 +264,7 @@
</p>
<p>
To check the most important PEAR settings (classpath, datapath, ...), or to read the settings with an
- application a <code>setenv.txt</code> file containing all these information is generated in the
+ application a <code>setenv.txt</code> file containing the PEAR settings is generated in the
<code>metadata</code> directory during the installation.
</p>
<p>
@@ -293,21 +277,21 @@
UIMA application out of the box. For details about the PEAR descriptor, please refer to the
UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.specifier">
- PEAR package descriptor</a>
+ PEAR package descriptor</a>.
</p>
<p>
- To install a PEAR package you have two possibilities.
+ To install a PEAR package you have two options:
</p>
<p>
<ul>
<li>
- <h4>PearInstaller UI</h4>
+ <h4>PEAR Installer UI</h4>
<p>
- The PearInstaller UI is a standalone Swing application to install PEAR packages.
- AFter the PEAR package and the install directory is selected, the installaion is
+ The PEAR Installer UI is a standalone Swing application to install PEAR packages.
+ After the PEAR package and the install directory is selected, the installation is
performed and the installation and verification results are displayed. Out of the tool
- it is also possible to test the installed PEAR package directly using the Cas Visual Debugger.
- For more details about PearInstall, please refer to the UIMA documentation at
+ it is directly possible to test the installed PEAR package using the Cas Visual Debugger (CVD).
+ For more details about the PEAR Installer, please refer to the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tools/tools.html#ugr.tools.pear.installer">
PEAR Installer User's Guide</a>.
</p>
@@ -315,10 +299,10 @@
<li>
<h4>PEAR API</h4>
<p>
- The PearInstaller API should be used if you want to integrate the PEAR installation
+ The PEAR API should be used if you want to integrate the PEAR installation
with a custom application. With the PEAR API it is possible to install PEAR packages
to a given installation directory and to optional verify the installed packages.
- Details about the PearInstaller API are available in the UIMA documentation at
+ Details about the PEAR API are available in the UIMA documentation at
<a href="http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.pear.installing_pear_using_API">
Installing a PEAR file using the PEAR APIs</a>.
</p>
@@ -340,7 +324,7 @@
The PEAR package descriptor can be treated similar to an analysis engine descriptor. It can be added
at any place where an analysis engine descriptor or cas consumer descriptor can be used. So for example
to run an installed PEAR package in the CAS Visual Debugger or in the Document Analyzer just use
- the PEAR package descriptor as analysis engine - and you don't have to take care about classpath
+ the PEAR package descriptor as analysis engine - you don't have to take care about classpath
and datapath settings.
</p>
<p>