Integration Reference Implementation for the ARCHER Metadata Editor
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Introduction
~~~~~~~~~~~~
  This file describes how to build the University of Queensland eResearch Unit
  Metadata Editor Reference Implementation projects.
  Refer to the README for overview and dependencies.


Dependencies
~~~~~~~~~~~~
  In addition to the dependencies specified in the general README file,
  this project requires the following components to be installed.
  Refer to their documentation for build and deployment instructions.

   au.edu.archer.metadata.spi   Metadata Service Provider Interface (SPI)
     - archer-server-metaservice.jar
       Deployed at runtime as described in the SPI_README fie.
     - archer-client-metaservice.jar
       Only required on the classpath if the SPI package is to be
       compiled.

   au.edu.archer.metadata.mde   Metadata Editor (MDE)
     - mde.war
       Required to run the application demonstration code



Eclipse Environment
~~~~~~~~~~~~~~~~~~~
 * Install EasyEclipse 1.2.2.2 Java Server ditro (includes Eclipse 3.2.2)
    http://easyeclipse.org/site/distributions/index.html

 * Install Tomcat 5.5.x .

 * Configure the Sysdeo Tomcat plugin (included with EasyEclipse)
    Navigate to: Eclipse | Windows | Preferences ... | Tomcat
    * Select Tomcat 5.5 and point it to your Tomcat 5.5. installation directory.

    Use 'Context files' as the context declaration mode.
    Context files may not be needed if you have deployed the SPI JAR to
    $CATALINA_HOME/common/lib and cofigured a global context.xml to
    reference the SPI record broker
      (See au.edu.archer.metadata.spi/doc/README.txt for details).

  Alternately, deploy the WAR files to a Tomcat server in the usual way
  after building them with the ant scripts to test the application in
  in a more real-world environment.  This is slower than using the
  process detailed above as changes require rebuild and redeploy, but
  it does provide confidence that things are working by plan rather
  than by coincidence.


Building
~~~~~~~~

  ** Eclipse **
  Should just autobuild.  Ensure that your project is configured
  to use the Sysdeo plugin and that it compiles classes into web/WEB_INF/classes .
  It should then use the project's .tomcatplugin file (hidden in Eclipse) to configure itself.

  ** Ant Build **
  Examine the build.xml for current details.  Briefly, the main targets are:

  - clean : Removes work directories used by the ant build
  - wars  : builds the WAR file, placing it in <project home>/build/release
  - deploy.tomcat : copies the WAR file to $CATALINA_HOME/webapps




                                    -oOo-